From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: lrn1986@gmail.com, gdb-patches@sourceware.org
Subject: Re: Warning when using separate debug info file
Date: Fri, 03 May 2019 07:05:00 -0000 [thread overview]
Message-ID: <83ef5gnhla.fsf@gnu.org> (raw)
In-Reply-To: <87o94kwwe6.fsf@tromey.com> (message from Tom Tromey on Thu, 02 May 2019 12:20:49 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: tom@tromey.com, lrn1986@gmail.com, gdb-patches@sourceware.org
> Date: Thu, 02 May 2019 12:20:49 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Eli> That bug report was resolved by a change in BFD, see
>
> Eli> https://sourceware.org/bugzilla/show_bug.cgi?id=24493#c8
>
> Eli> Will this commit automatically appear in GDB 8.3? I'm guessing not,
> Eli> and if so, what should I do to make it so? And do people agree to
> Eli> backport this change to the 8.3 branch to begin with?
>
> It seems safe enough to me. To get it into 8.3, you would cherry-pick
> the commit to the 8.3 branch.
Thanks, done.
next prev parent reply other threads:[~2019-05-03 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83y348edoi.fsf@gnu.org>
2019-04-17 20:06 ` LRN
2019-04-18 12:53 ` Eli Zaretskii
2019-04-18 15:53 ` LRN
2019-04-18 18:30 ` Eli Zaretskii
2019-04-24 19:28 ` Tom Tromey
2019-04-24 19:39 ` Eli Zaretskii
2019-04-25 13:46 ` Tom Tromey
2019-04-25 15:02 ` Eli Zaretskii
2019-04-25 15:49 ` Tom Tromey
2019-04-25 16:19 ` Eli Zaretskii
2019-04-25 17:31 ` Tom Tromey
2019-04-27 15:19 ` Eli Zaretskii
2019-04-27 15:37 ` Eli Zaretskii
2019-05-02 15:50 ` Eli Zaretskii
2019-05-02 18:20 ` Tom Tromey
2019-05-03 7:05 ` Eli Zaretskii [this message]
2019-04-24 19:49 ` André Pönitz
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=83ef5gnhla.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lrn1986@gmail.com \
--cc=tom@tromey.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