From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "Dmitry.Neverov" <dmitry.neverov@jetbrains.com>,
tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PR 31727] Recognize -2 as a tombstone value in .debug_line
Date: Wed, 04 Sep 2024 11:58:11 -0600 [thread overview]
Message-ID: <871q1z5mj0.fsf@tromey.com> (raw)
In-Reply-To: <ZtYAmhiF/nm0AQWG@adacore.com> (Joel Brobecker's message of "Mon, 2 Sep 2024 11:14:50 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> You are right that separate approval for gdb-15-branch is necessary.
Joel> Hoping that Tom sees this message and can confirm it's OK for the
Joel> branch.
Sorry about the delay on this. I agree it's ok for the gdb-15 branch.
Tom
prev parent reply other threads:[~2024-09-04 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 8:45 Dmitry Neverov
2024-06-08 8:53 ` Dmitry.Neverov
2024-06-10 20:29 ` Tom Tromey
[not found] ` <87cyohxdim.fsf@lubuntu2.mail-host-address-is-not-set>
2024-08-18 6:00 ` [PING][PR " Dmitry.Neverov
2024-08-23 16:16 ` Tom Tromey
2024-09-01 18:50 ` [PR " Joel Brobecker
2024-09-02 17:55 ` Dmitry.Neverov
2024-09-02 18:14 ` Joel Brobecker
2024-09-04 17:58 ` 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=871q1z5mj0.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=dmitry.neverov@jetbrains.com \
--cc=gdb-patches@sourceware.org \
/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