From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: MinGW build of GDB 13 snapshot
Date: Fri, 23 Dec 2022 07:28:54 +0400 [thread overview]
Message-ID: <Y6UgdhdpGaM4EMi9@adacore.com> (raw)
In-Reply-To: <83tu1n90nd.fsf@gnu.org>
Hi Eli,
On Thu, Dec 22, 2022 at 12:46:14PM +0200, Eli Zaretskii wrote:
> > Date: Wed, 21 Dec 2022 07:26:49 +0400
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: Tom Tromey <tom@tromey.com>, brobecker@adacore.com,
> > gdb-patches@sourceware.org
> >
> > > The problem is now fixed in upstream Binutils, see
> > >
> > > https://sourceware.org/bugzilla/show_bug.cgi?id=29915
> > >
> > > So I think I will fix this on the gdb 13 branch only, and master will
> > > be fixed in due time when we import the latest BFD? Or do you want me
> > > to fix this on both branches? Joel?
> >
> > Binutils and GDB share the same repository, so it's the same master
> > branch. Alan's fix on master, if you confirm fixes the problem on
> > master, can be cherry-picked to the gdb-13-branch.
> >
> > Otherwise, if Alan's fix does not work, we can indeed start with
> > your patch in gdb-13-branch, and wait for master to get fixed
> > via the binutils team.
>
> OK, done.
>
> I also installed the other patch, approved by Tom.
Thank you.
Just for the avoidance of doubt: On the gdb-13-branch, I see
you cherry-picked Alan's change and then applied the fix for
the other issue you noticed.
What about master? Alan's change was pushed by Alan himself
a few days ago, but what about the fix for the other issue?
Did you push it there as well? I don't seem to be able to
see it.
--
Joel
next prev parent reply other threads:[~2022-12-23 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 17:16 Eli Zaretskii
2022-12-19 21:14 ` Tom Tromey
2022-12-20 14:12 ` Eli Zaretskii
2022-12-21 3:26 ` Joel Brobecker
2022-12-22 10:46 ` Eli Zaretskii
2022-12-23 3:28 ` Joel Brobecker [this message]
2022-12-23 8:07 ` Eli Zaretskii
2022-12-23 9:13 ` Joel Brobecker
2022-12-23 11:21 ` Eli Zaretskii
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=Y6UgdhdpGaM4EMi9@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).