From: Tom Tromey <tom@tromey.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: Tom Tromey <tom@tromey.com>,
Alan Modra via Gdb <gdb@sourceware.org>,
Alan Modra <amodra@gmail.com>,
binutils <binutils@sourceware.org>,
Nick Clifton <nickc@redhat.com>
Subject: Re: Syncing the toplevel with the GCC tree
Date: Wed, 02 Aug 2023 15:03:58 -0600 [thread overview]
Message-ID: <87fs5188ch.fsf@tromey.com> (raw)
In-Reply-To: <87msz9y2aw.fsf@aarsen.me> ("Arsen =?utf-8?Q?Arsenovi=C4=87?= =?utf-8?Q?=22's?= message of "Wed, 02 Aug 2023 15:49:21 +0200")
>>>>> "Arsen" == Arsen Arsenović <arsen@aarsen.me> writes:
Arsen> Thanks for the tips. I've gone ahead and cherry picked (by adding my
Arsen> gcc checkout as a remote in my binutils-gdb checkout and vice-versa)
Arsen> most diverging patches from each repo.
Arsen> This approach also retains authorship information (though, I will have
Arsen> to comb over the resulting commits to add context and adjust commit
Arsen> messages).
Arsen> A few manual interventions remain, and I've yet to synchronize the
Arsen> libtool forks and re-do testing.
Thank you for taking this on.
Tom
prev parent reply other threads:[~2023-08-02 21:04 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
2023-08-02 13:49 ` Arsen Arsenović
2023-08-02 21:03 ` 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=87fs5188ch.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).