From: Tom Tromey <tom@tromey.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add some new DW_IDX_* constants
Date: Sun, 10 Dec 2023 13:59:12 -0700 [thread overview]
Message-ID: <87cyvd7p0f.fsf@tromey.com> (raw)
In-Reply-To: <ZXTkHpwP1yGsSYNP@tucnak> (Jakub Jelinek's message of "Sat, 9 Dec 2023 23:03:10 +0100")
>>>>> "Jakub" == Jakub Jelinek <jakub@redhat.com> writes:
Jakub> LGTM for GCC (but it needs a ChangeLog entry).
Oops, yeah -- I am out of the habit of writing those.
I'll add one before I push this.
Tom
prev parent reply other threads:[~2023-12-10 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 20:56 Tom Tromey
2023-12-09 22:03 ` Jakub Jelinek
2023-12-10 20:59 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyvd7p0f.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jakub@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox