From: Tom Tromey <tom@tromey.com>
To: Alan Modra via Gdb <gdb@sourceware.org>
Cc: "Arsen Arsenović" <arsen@aarsen.me>,
"Alan Modra" <amodra@gmail.com>,
binutils <binutils@sourceware.org>,
"Nick Clifton" <nickc@redhat.com>
Subject: Re: Syncing the toplevel with the GCC tree
Date: Fri, 28 Jul 2023 08:12:04 -0600 [thread overview]
Message-ID: <87y1j0gm6j.fsf@tromey.com> (raw)
In-Reply-To: <ZMN59ZbR0WWHIMJC@squeak.grove.modra.org> (Alan Modra via Gdb's message of "Fri, 28 Jul 2023 17:49:01 +0930")
>>>>> "Alan" == Alan Modra via Gdb <gdb@sourceware.org> writes:
Alan> The process goes like this:
Alan> 1) Some ports have been removed from gcc but not binutils-gdb, so
Alan> firstly revert those patches to the top-level on the gcc side.
Alan> 2) Copy over the gcc configury and makefiles.
FWIW, when I was doing some merges from GCC, what I generally did is
find the upstream patches, "git format-patch" them, then "git am" them
into the binutils-gdb tree, fixing up problems along the way.
Tom
next prev parent reply other threads:[~2023-07-28 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 13:47 Arsen Arsenović
2023-07-28 8:19 ` Alan Modra
2023-07-28 14:12 ` Tom Tromey [this message]
2023-08-02 13:49 ` Arsen Arsenović
2023-08-02 21:03 ` Tom Tromey
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=87y1j0gm6j.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amodra@gmail.com \
--cc=arsen@aarsen.me \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).