From: Antony Polukhin <antoshkka@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR libstdc++/71579 assert that type traits are not misused with an incomplete type
Date: Fri, 31 May 2019 05:58:00 -0000 [thread overview]
Message-ID: <CAKqmYPZXswTHBx0aw9c5+8k4qUb2Rr-ZKZ+0fE_OOjQ2wOtWUA@mail.gmail.com> (raw)
In-Reply-To: <20190530163808.GP2599@redhat.com>
On Thu, May 30, 2019, 19:38 Jonathan Wakely <jwakely@redhat.com> wrote:
<...>
> I've attached a relative diff, to be applied on top of yours, with my
> suggested tweaks. Do you see any issues with it?
>
> (If you're happy with those tweaks I can go ahead and apply this,
> there's no need for an updated patch from you).
>
Looks good. Please apply!
>
next prev parent reply other threads:[~2019-05-31 5:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 11:20 Antony Polukhin
2019-05-08 21:10 ` Jonathan Wakely
2019-05-30 6:07 ` Antony Polukhin
2019-05-30 16:38 ` Jonathan Wakely
2019-05-31 5:58 ` Antony Polukhin [this message]
2019-05-31 10:36 ` Jonathan Wakely
2019-06-06 12:19 ` Jonathan Wakely
2019-06-20 17:49 ` Antony Polukhin
2019-06-20 17:57 ` Ville Voutilainen
2019-06-20 18:56 ` Antony Polukhin
2020-08-12 8:19 ` Antony Polukhin
2020-08-19 11:29 ` Jonathan Wakely
2020-08-19 16:44 ` Antony Polukhin
2020-08-20 15:31 ` Antony Polukhin
2020-09-24 7:15 ` Antony Polukhin
2020-09-24 9:29 ` Jonathan Wakely
2020-09-24 17:53 ` Jonathan Wakely
2020-11-12 18:55 ` Antony Polukhin
2021-01-08 17:28 ` Antony Polukhin
2021-05-07 18:00 ` Antony Polukhin
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=CAKqmYPZXswTHBx0aw9c5+8k4qUb2Rr-ZKZ+0fE_OOjQ2wOtWUA@mail.gmail.com \
--to=antoshkka@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).