From: Jonathan Wakely <jwakely@redhat.com>
To: Marco Falke <falke.marco@gmail.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Re: [PATCH] libstdc++: Make __from_chars_alnum_to_val conversion explicit
Date: Tue, 19 Jul 2022 11:15:45 +0100 [thread overview]
Message-ID: <CACb0b4=SZ=BYN8nwhY6Bz+Ez3gZqg+9UZZvACHS3hhpj71o0=A@mail.gmail.com> (raw)
In-Reply-To: <CAK51vgBFXHRy=4L_UYZ2KQZqEFDw-Fur9WTnPfuark+es8UOmQ@mail.gmail.com>
On Tue, 19 Jul 2022 at 11:13, Marco Falke <falke.marco@gmail.com> wrote:
>
> Thanks Jonathan. Either name is perfectly fine.
OK, thanks.
>
> To clarify, this will be pushed to master and also backported to the 12-branch?
Yes, that's right. It will go to trunk (aka master) today and then
backported to the gcc-12 branch "soon" (whenever I do the next batch
of backports, which might be later this week).
prev parent reply other threads:[~2022-07-19 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 10:10 Marco Falke
2022-07-19 10:06 ` Jonathan Wakely
2022-07-19 10:13 ` Marco Falke
2022-07-19 10:15 ` Jonathan Wakely [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='CACb0b4=SZ=BYN8nwhY6Bz+Ez3gZqg+9UZZvACHS3hhpj71o0=A@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=falke.marco@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).