public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Alan Modra <amodra@gmail.com>
Cc: Tom de Vries <tdevries@suse.de>, <gdb-patches@sourceware.org>,
	<binutils@sourceware.org>
Subject: Re: [RFC][top-level] Add configure test-case
Date: Mon, 7 Nov 2022 18:23:45 +0000	[thread overview]
Message-ID: <6a0ccc2-e4ab-c8f0-dffc-cd8f0f1369b@codesourcery.com> (raw)
In-Reply-To: <Y2jtVHkvM9ejHwVd@squeak.grove.modra.org>

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.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2022-11-07 18:23 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 [this message]
2022-11-08  7:12     ` Alan Modra
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=6a0ccc2-e4ab-c8f0-dffc-cd8f0f1369b@codesourcery.com \
    --to=joseph@codesourcery.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.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).