From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Jonny Grant <jg@jguk.org>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Fwd: Fwd: [PATCH] update copyright year in libstdcc++ manual
Date: Sat, 4 Mar 2023 14:50:31 +0000 [thread overview]
Message-ID: <CAH6eHdSQRcUoBTCC0sOV0NmqAFwgmgHcnC1xURnsMy8aySkABg@mail.gmail.com> (raw)
In-Reply-To: <490cf7461f1b52593d4fce9fd8d4dff023cf88e4.camel@xry111.site>
On Sat, 4 Mar 2023 at 13:31, Xi Ruoyao via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> On Sat, 2023-03-04 at 13:13 +0000, Jonny Grant wrote:
> > Hello
> > Is this something someone here could review please? I don't have write
> > access.
>
> Don't forward a patch everywhere, just ping it. See the section about
> pinging a patch in https://gcc.gnu.org/contribute.html.
Patches for libstdc++ should be sent to both gcc-patches and the
libstdc++ list (but not gcc-help). That's why this one wasn't reviewed
or applied.
next prev parent reply other threads:[~2023-03-04 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fc9664e8-65e9-00ef-25c4-4766fd70e12e@jguk.org>
2023-03-04 13:13 ` Jonny Grant
2023-03-04 13:31 ` Xi Ruoyao
2023-03-04 14:50 ` Jonathan Wakely [this message]
2023-03-04 15:04 ` Jonny Grant
2023-03-04 17:58 ` Jonathan Wakely
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=CAH6eHdSQRcUoBTCC0sOV0NmqAFwgmgHcnC1xURnsMy8aySkABg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jg@jguk.org \
--cc=xry111@xry111.site \
/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).