From: Tom Honermann <tom@honermann.net>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/2]: C N2653 char8_t implementation
Date: Tue, 11 Jan 2022 14:03:41 -0500 [thread overview]
Message-ID: <d0e7b373-ec5c-bd1c-c312-146728b4ed39@honermann.net> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2201110221280.444240@digraph.polyomino.org.uk>
On 1/10/22 9:23 PM, Joseph Myers wrote:
> Please repost these patches after GCC 12 branches (updated as appropriate
> depending on whether the feature is accepted at the two-week Jan/Feb WG14
> meeting, which doesn't yet have an agenda), since we're currently
> stabilizing for the release and so not considering new features.
>
Thank you, Joseph. Will do!
Tom.
prev parent reply other threads:[~2022-01-11 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 0:42 Tom Honermann
2022-01-11 2:23 ` Joseph Myers
2022-01-11 19:03 ` Tom Honermann [this message]
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=d0e7b373-ec5c-bd1c-c312-146728b4ed39@honermann.net \
--to=tom@honermann.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).