public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>, Xi Ruoyao <xry111@xry111.site>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Fwd: Fwd: [PATCH] update copyright year in libstdcc++ manual
Date: Sat, 4 Mar 2023 15:04:33 +0000	[thread overview]
Message-ID: <59914321-c694-8092-5cbf-bfea10559370@jguk.org> (raw)
In-Reply-To: <CAH6eHdSQRcUoBTCC0sOV0NmqAFwgmgHcnC1xURnsMy8aySkABg@mail.gmail.com>



On 04/03/2023 14:50, Jonathan Wakely wrote:
> 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.

Fair enough, I can re-work it, unless simpler for you to re-do it?

Where is the best place to email spelling mistakes in libstdc++ files?
Kind regards, Jonny

  reply	other threads:[~2023-03-04 15:04 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
2023-03-04 15:04       ` Jonny Grant [this message]
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=59914321-c694-8092-5cbf-bfea10559370@jguk.org \
    --to=jg@jguk.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --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).