From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/2] gdb: Require a C++11 compiler
Date: Fri, 28 Oct 2016 12:07:00 -0000 [thread overview]
Message-ID: <CAH=s-PNPnWa8jznFhB+OdRV2itX3mFEBOOwzkG6DEgx1RGeOXQ@mail.gmail.com> (raw)
In-Reply-To: <1477596094-3244-1-git-send-email-palves@redhat.com>
On Thu, Oct 27, 2016 at 8:21 PM, Pedro Alves <palves@redhat.com> wrote:
> As previously discussed, this patch set makes GDB require a C++11
> compiler.
>
> You'll find the previous discussions referenced here:
> https://sourceware.org/ml/gdb-patches/2016-10/msg00607.html
>
> This is basically the same as I had sent here:
> https://sourceware.org/ml/gdb-patches/2016-10/msg00336.html
>
> The only difference is a single-line change that makes C++11 a
> mandatory instead of enabling it iff supported.
>
This series is good to me.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-10-28 12:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 19:21 Pedro Alves
2016-10-27 19:21 ` [PATCH 2/2] gdb: Require C++11 Pedro Alves
[not found] ` <20161028104718.540c10ed@ThinkPad>
2016-10-28 9:03 ` Pedro Alves
2016-10-28 10:44 ` Philipp Rudo
2016-11-03 15:39 ` Yao Qi
2016-11-03 15:58 ` Pedro Alves
2016-11-03 16:11 ` Yao Qi
2016-10-27 19:21 ` [PATCH 1/2] gdb: Import AX_CXX_COMPILE_STDCXX from the GNU Autoconf Archive Pedro Alves
2016-10-28 12:07 ` Yao Qi [this message]
2016-10-28 15:08 ` [PATCH 0/2] gdb: Require a C++11 compiler Pedro Alves
2016-10-28 17:17 ` [PATCH] gdb/NEWS: Mention C++11 requirement Pedro Alves
2016-10-29 6:13 ` Eli Zaretskii
2016-10-29 15:18 ` Pedro Alves
2016-10-29 15:29 ` Eli Zaretskii
2016-10-29 15:35 ` Pedro Alves
2016-11-01 11:00 ` [PATCH 0/2] gdb: Require a C++11 compiler Richard Earnshaw (lists)
2016-11-01 16:53 ` Pedro Alves
2016-11-02 14:51 ` Richard Earnshaw (lists)
2016-11-02 15:58 ` Pedro Alves
2016-11-04 13:31 ` Maciej W. Rozycki
2016-11-04 14:46 ` Pedro Alves
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='CAH=s-PNPnWa8jznFhB+OdRV2itX3mFEBOOwzkG6DEgx1RGeOXQ@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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