public inbox for
 help / color / mirror / Atom feed
From: Alexandre Oliva <>
To: Alan Modra via Gdb-patches <>
Cc: Joseph Myers <>,
	Alan Modra <>, Tom de Vries <>,,,,,
Subject: Re: [RFC][top-level] Add configure test-case
Date: Sat, 14 Jan 2023 05:51:16 -0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Alan Modra via Gdb-patches's message of "Tue, 8 Nov 2022 17:42:17 +1030")

On Nov  8, 2022, Alan Modra via Gdb-patches <> wrote:

> 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?

FTR, II've long assumed that this cooperation in maintaining the
top-level build machinery worked both ways already.  Reducing divergence
is a plus IMHO.

Alexandre Oliva, happy hacker      
   Free Software Activist                       GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <>

      reply	other threads:[~2023-01-14  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 15:10 Tom de Vries
2022-10-31 15:03 ` Nick Clifton
2022-11-07 11:34 ` Alan Modra
2022-11-07 18:23   ` Joseph Myers
2022-11-08  7:12     ` Alan Modra
2023-01-14  8:51       ` Alexandre Oliva [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* 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).