From: Thomas Rodgers <trodgers@redhat.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++\@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] Clean up non-conforming names
Date: Tue, 11 Jun 2019 18:05:00 -0000 [thread overview]
Message-ID: <xkqey328huaw.fsf@trodgers.remote.f27> (raw)
In-Reply-To: <xkqeo93fkb1p.fsf@trodgers.remote.f27>
Tested x86_64-linux, committed to trunk.
Thomas Rodgers writes:
> Jonathan Wakely writes:
>
>> On 31/05/19 17:15 -0700, Thomas Rodgers wrote:
>>>
>>>Revising previous version of this patch to pick another missed
>>>uglification.
>>
>> OK for trunk, thanks.
>>
>> I also see this one:
>>
>> include/pstl/parallel_backend_tbb.h: __buffer(std::size_t n) : _M_allocator(), _M_ptr(_M_allocator.allocate(n)), _M_buf_size(n) {}
>
> Ok, I'll clean that one up and commit along with these changes.
prev parent reply other threads:[~2019-06-11 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 20:50 Thomas Rodgers
2019-06-01 0:15 ` Thomas Rodgers
2019-06-01 11:43 ` Jonathan Wakely
2019-06-02 20:05 ` Thomas Rodgers
2019-06-11 18:05 ` Thomas Rodgers [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=xkqey328huaw.fsf@trodgers.remote.f27 \
--to=trodgers@redhat.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).