From: Alan Modra <amodra@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Tom de Vries <tdevries@suse.de>,
gdb-patches@sourceware.org, binutils@sourceware.org,
gcc@gcc.gnu.org, bonzini@gnu.org, neroden@gcc.gnu.org,
aoliva@gcc.gnu.org, Ralf.Wildenhues@gmx.de
Subject: Re: [RFC][top-level] Add configure test-case
Date: Tue, 8 Nov 2022 17:42:17 +1030 [thread overview]
Message-ID: <Y2oBUTBx7NhMsCgW@squeak.grove.modra.org> (raw)
In-Reply-To: <6a0ccc2-e4ab-c8f0-dffc-cd8f0f1369b@codesourcery.com>
On Mon, Nov 07, 2022 at 06:23:45PM +0000, Joseph Myers wrote:
> On Mon, 7 Nov 2022, Alan Modra via Binutils wrote:
>
> > a) that top-level binutils/gdb patches don't get applied to the gcc
> > git repository in a timely manner, or
>
> If a toplevel patch is approved for either repository, I think you should
> treat it as approved for the other one without needing separate review.
Thanks Joseph, that's how I see it too. Of course with the
understanding that binutils-gdb can't be used as a back door way of
sneaking in a gcc-specific change.
Can I get agreement among the gcc build maintainers that such a
policy is acceptable?
--
Alan Modra
Australia Development Lab, IBM
next parent reply other threads:[~2022-11-08 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221020151027.GA1300@delia.home>
[not found] ` <Y2jtVHkvM9ejHwVd@squeak.grove.modra.org>
[not found] ` <6a0ccc2-e4ab-c8f0-dffc-cd8f0f1369b@codesourcery.com>
2022-11-08 7:12 ` Alan Modra [this message]
2023-01-14 8:51 ` Alexandre Oliva
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=Y2oBUTBx7NhMsCgW@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@gcc.gnu.org \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=neroden@gcc.gnu.org \
--cc=tdevries@suse.de \
/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).