From: Jonathan Wakely <jwakely@redhat.com>
To: Mark Mentovai <mark@mentovai.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>,
Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [PATCH] libstdc++: Rename __null_terminated to avoid collision with Apple SDK
Date: Mon, 13 Jun 2022 20:28:58 +0100 [thread overview]
Message-ID: <CACb0b4maOr40S_bQPM-D3isgYiM4daV7HqwsijSLEbYqN9K86A@mail.gmail.com> (raw)
In-Reply-To: <CAO5tm1tc0gVBisVXc=dqGj7NfNwdoKnoZiYoO3aBkcDoEOfJaw@mail.gmail.com>
On Fri, 10 Jun 2022 at 22:42, Mark Mentovai wrote:
>
> Thanks, Jonathan. I am, in fact, so certifying.
Great, thanks.
>
> I do believe that bringing up support for new OS versions is in scope for open branches, and it makes sense to merge, particularly for a trivial and uncontentious patch like this one.
Agreed. I've pushed it to trunk for now and will follow up with the
backports soon.
Thanks again for the patch.
prev parent reply other threads:[~2022-06-13 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 20:11 Mark Mentovai
2022-06-10 21:21 ` Jonathan Wakely
2022-06-10 21:42 ` Mark Mentovai
2022-06-13 19:28 ` 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=CACb0b4maOr40S_bQPM-D3isgYiM4daV7HqwsijSLEbYqN9K86A@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=libstdc++@gcc.gnu.org \
--cc=mark@mentovai.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).