From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/NEWS: Mention C++11 requirement
Date: Sat, 29 Oct 2016 15:29:00 -0000 [thread overview]
Message-ID: <838tt7qiky.fsf@gnu.org> (raw)
In-Reply-To: <10b3ff78-b007-9088-ee8c-c3282df1c0b4@redhat.com> (message from Pedro Alves on Sat, 29 Oct 2016 16:18:50 +0100)
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Sat, 29 Oct 2016 16:18:50 +0100
>
> Reading the text back, I wonder if this would sound
> clearer/more natural:
>
> -* GDB and GDBserver now require building with a C++11 compiler.
> +* Building GDB and GDBserver now requires a C++11 compiler.
The latter is better, indeed.
next prev parent reply other threads:[~2016-10-29 15:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 19:21 [PATCH 0/2] gdb: Require a C++11 compiler 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 ` [PATCH 0/2] gdb: Require a C++11 compiler Yao Qi
2016-10-28 15:08 ` 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 [this message]
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=838tt7qiky.fsf@gnu.org \
--to=eliz@gnu.org \
--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