public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Huanghui Nie <nnnjkk@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Sam James <sam@gentoo.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: hashtable: No need to update before begin node in _M_remove_bucket_begin
Date: Wed, 17 Jan 2024 18:30:00 +0800	[thread overview]
Message-ID: <CAOv15-XkFoTqzdTOLNtF6U_KQR6hzTka_STnAFz_aHvJzCO7jQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdR2uRrNBST+wuWT-=vibGWQN+H7FfwUULn0HQGV5LTgSQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

I'm sorry for CC the gcc@ list. Waiting for your review results there.
Thanks.

2024年1月17日(水) 16:18 Jonathan Wakely <jwakely.gcc@gmail.com>:

>
>
> On Wed, 17 Jan 2024, 08:14 Huanghui Nie via Gcc, <gcc@gcc.gnu.org> wrote:
>
>> Thanks. Done.
>>
>
> And don't CC the main gcc@ list, that's not for patch discussion. And if
> you CC the right list, you don't need to CC the individual maintainers.
>
> Anyway, it's on the right list now so we'll review it there, thanks.
>
>
>
>> 2024年1月17日(水) 12:39 Sam James <sam@gentoo.org>:
>>
>> >
>> > Huanghui Nie <nnnjkk@gmail.com> writes:
>> >
>> > > Hi.
>> >
>> > Please CC the libstdc++ LM for libstdc++ patches, per
>> >
>> >
>> https://gcc.gnu.org/onlinedocs/libstdc++/manual/appendix_contributing.html#list.patches
>> > .
>> >
>> > > [...]
>> >
>> >
>>
>

  reply	other threads:[~2024-01-17 10:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17  4:19 Huanghui Nie
2024-01-17  4:39 ` Sam James
2024-01-17  8:12   ` Huanghui Nie
2024-01-17  8:18     ` Jonathan Wakely
2024-01-17 10:30       ` Huanghui Nie [this message]
2024-01-17  8:11 Huanghui Nie
2024-01-17 20:04 ` François Dumont
2024-01-18  9:26   ` Huanghui Nie
2024-01-22  6:14     ` François Dumont

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=CAOv15-XkFoTqzdTOLNtF6U_KQR6hzTka_STnAFz_aHvJzCO7jQ@mail.gmail.com \
    --to=nnnjkk@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=sam@gentoo.org \
    /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).