From: Tom Honermann <tom@honermann.net>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/3]: C++20 P0482R6 and C2X N2653: Implement mbrtoc8, c8rtomb, char8_t
Date: Sat, 22 Jan 2022 07:24:36 -0500 [thread overview]
Message-ID: <021f1f3c-55ad-888c-0852-ffc1aba8d7f0@honermann.net> (raw)
In-Reply-To: <386a928a-1fdc-d2c9-8815-0e39ee5fb873@linaro.org>
On 1/21/22 3:01 PM, Adhemerval Zanella wrote:
>
> On 20/01/2022 20:17, Tom Honermann via Libc-alpha wrote:
>> On 1/11/22 2:23 PM, Tom Honermann via Libc-alpha wrote:
>>> On 1/10/22 7:53 PM, Joseph Myers wrote:
>>>> This patch is adding a NEWS entry for 2.34. Since the next release is
>>>> 2.35, it should add an entry there instead (except we've started release
>>>> slush for 2.35, so it might be better to aim this at 2.36).
>>>>
>>> Thank you for spotting that; this was due to a bad merge conflict resolution on my part. Fixed patch attached.
>>>
>>> If this needs to wait for 2.36, I understand, but I would love to have this in 2.35 to close out this gap in C++20 support.
>> Any further comments on this patch series?
>>
>> Tom.
>>
> I think it is too late for 2.35, but I will take to check when 2.36 opens.
I understand. Thank you! I'll repost the patch series with the changes
needed for 2.36 once 2.35 is released.
Tom.
next prev parent reply other threads:[~2022-01-22 12:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 0:39 Tom Honermann
2022-01-11 0:53 ` Joseph Myers
2022-01-11 19:23 ` Tom Honermann
2022-01-20 23:17 ` Tom Honermann
2022-01-21 20:01 ` Adhemerval Zanella
2022-01-22 12:24 ` Tom Honermann [this message]
2022-02-16 18:29 ` Joseph Myers
2022-02-16 19:14 ` tom
-- strict thread matches above, loose matches on Subject: below --
2022-02-27 16:53 Tom Honermann
2022-02-28 23:01 ` Joseph Myers
2022-03-01 3:40 ` Tom Honermann
2022-05-17 15:57 ` Carlos O'Donell
2022-05-17 18:05 ` Adhemerval Zanella
2022-05-17 18:12 ` Joseph Myers
2022-05-17 18:17 ` Adhemerval Zanella
2022-05-17 21:33 ` Florian Weimer
2022-05-18 15:32 ` Tom Honermann
2022-05-18 16:17 ` Adhemerval Zanella
2022-05-18 17:26 ` Tom Honermann
2022-05-18 17:39 ` Adhemerval Zanella
2022-05-18 17:40 ` Florian Weimer
2022-05-18 17:57 ` Adhemerval Zanella
2021-06-07 2:08 Tom Honermann
2021-06-07 18:53 ` Joseph Myers
2021-06-11 11:25 ` Tom Honermann
2021-06-11 16:28 ` Joseph Myers
2021-06-13 15:35 ` Tom Honermann
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=021f1f3c-55ad-888c-0852-ffc1aba8d7f0@honermann.net \
--to=tom@honermann.net \
--cc=adhemerval.zanella@linaro.org \
--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).