From: Sam James <sam@gentoo.org>
To: Huanghui Nie <nnnjkk@gmail.com>
Cc: gcc@gcc.gnu.org, 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 04:39:15 +0000 [thread overview]
Message-ID: <87wms8po8g.fsf@gentoo.org> (raw)
In-Reply-To: <CAOv15-WGGF4_fqeSjw7DX58qBRGW4P3e-LfG=bsSQsLLyXtUeQ@mail.gmail.com>
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.
> [...]
next prev parent reply other threads:[~2024-01-17 4:39 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 [this message]
2024-01-17 8:12 ` Huanghui Nie
2024-01-17 8:18 ` Jonathan Wakely
2024-01-17 10:30 ` Huanghui Nie
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=87wms8po8g.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=nnnjkk@gmail.com \
/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).