From: "罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Jens Gustedt <jens.gustedt@inria.fr>, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/5] features: Rename __GLIBC_USE_ISOC2X to __GLIBC_USE_ISOC23
Date: Wed, 21 Jun 2023 14:32:29 +0800 [thread overview]
Message-ID: <CAE2XoE_Zyr5p1JQK-G2U9WE-rr25K6Z9NmGYN8A-ry_E+hREwA@mail.gmail.com> (raw)
In-Reply-To: <79d6efd8-d6ce-e7b7-4895-c9b1df8f9687@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Wed, Jun 21, 2023 at 4:21 AM Joseph Myers <joseph@codesourcery.com>
wrote:
>
> Why? You do realise that the DIS ballot resolution isn't until 2024, and
This patch dropped.
> it's entirely plausible that we end up with an FDIS if there are any
> technical comments on the DIS ballot? We haven't actually discussed
> whether to *call* it C24, or whether to increase the __STDC_VERSION__
> value (and other associated values), yet at the current meeting (if that's
> to be discussed, Other Business would be the natural agenda item), but it
> seems extremely premature to suppose the name will be C23, and rename
> internal interfaces accordingly, when we know WG14 don't be done with it
> until January 2024 at the earliest, or several months later if an FDIS is
> needed.
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
next prev parent reply other threads:[~2023-06-21 6:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 22:20 [PATCH 0/5] c2y proposal add monotonicwait support for mtx and ctx Yonggang Luo
2023-06-19 22:20 ` [PATCH 1/5] features: Rename __GLIBC_USE_ISOC2X to __GLIBC_USE_ISOC23 Yonggang Luo
2023-06-20 20:21 ` Joseph Myers
2023-06-21 6:32 ` 罗勇刚(Yonggang Luo) [this message]
2023-06-19 22:20 ` [PATCH 2/5] time: Implement c23 timespec_get base Yonggang Luo
2023-06-20 12:44 ` Florian Weimer
2023-06-20 16:10 ` 罗勇刚(Yonggang Luo)
2023-06-20 20:25 ` Joseph Myers
2023-06-19 22:20 ` [PATCH 3/5] clang-format: should format with 2 space and do not usage tab Yonggang Luo
2023-06-19 22:20 ` [PATCH 4/5] c11: Switch to use pthread_mutex_clocklock and pthread_cond_clockwait to implement cnd and mtx lock and wait Yonggang Luo
2023-06-20 9:15 ` Florian Weimer
2023-06-19 22:20 ` [PATCH 5/5] c2y: Add function cnd_timedwait_monotonic and mtx_timedlock_monotonic Yonggang Luo
2023-06-20 20:29 ` Joseph Myers
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=CAE2XoE_Zyr5p1JQK-G2U9WE-rr25K6Z9NmGYN8A-ry_E+hREwA@mail.gmail.com \
--to=luoyonggang@gmail.com \
--cc=jens.gustedt@inria.fr \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).