From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add DISABLE_COPY_AND_ASSIGN
Date: Fri, 15 Sep 2017 12:05:00 -0000 [thread overview]
Message-ID: <864ls4rwu9.fsf@gmail.com> (raw)
In-Reply-To: <19cd9fec-2b41-e827-0d51-b2a1b0680808@ericsson.com> (Simon Marchi's message of "Sat, 9 Sep 2017 20:45:39 +0200")
Simon Marchi <simon.marchi@ericsson.com> writes:
> Out of curiosity, did you make any progress on this?
I pinged Ian in GNU Cauldron, and he is "basically OK" with the patch.
https://gcc.gnu.org/ml/gcc-patches/2017-09/msg00532.html
I need to address his comments and commit it.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-09-15 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 13:48 Yao Qi
2017-07-18 14:22 ` Pedro Alves
2017-07-18 15:13 ` Yao Qi
2017-07-18 15:38 ` Pedro Alves
2017-09-09 18:45 ` Simon Marchi
2017-09-15 12:05 ` Yao Qi [this message]
2017-09-19 9:13 ` Yao Qi
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=864ls4rwu9.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.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