From: Marco Falke <falke.marco@gmail.com>
To: Jonathan Wakely <jwakely@redhat.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 12:13:30 +0200 [thread overview]
Message-ID: <CAK51vgBFXHRy=4L_UYZ2KQZqEFDw-Fur9WTnPfuark+es8UOmQ@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4mVY19bGD7SfpZ7CUozg33ErCwH9fHpxePtv9dP4DFdnw@mail.gmail.com>
Thanks Jonathan. Either name is perfectly fine.
To clarify, this will be pushed to master and also backported to the 12-branch?
Best, Marco
On Tue, Jul 19, 2022 at 12:06 PM Jonathan Wakely <jwakely@redhat.com> wrote:
>
> On Mon, 18 Jul 2022 at 11:11, Marco Falke via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
> >
> > (in reply to https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598412.html,
> > adding libstdc++ to CC, with the same patch attached again)
> >
> > To clarify, this is not a fix for a user-facing issue of gcc or a fix
> > for UB. It is just a minor UX improvement for developers that use the
> > clang integer sanitizer to detect implicit int conversions.
>
> Thanks for the patch, I'm running tests now and will commit it once
> everything passes.
>
> As this is an obvious, non-copyrightable fix we don't need any
> paperwork of DCO sign-off for this change. Is it OK if I commit it for
> the name "Marco Falke" or do you want to use the Author Name
> "MacroFake" from the patch attachment?
>
> Thanks again.
>
next prev parent reply other threads:[~2022-07-19 10:13 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 [this message]
2022-07-19 10:15 ` Jonathan Wakely
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='CAK51vgBFXHRy=4L_UYZ2KQZqEFDw-Fur9WTnPfuark+es8UOmQ@mail.gmail.com' \
--to=falke.marco@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--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).