From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/NEWS: Mention C++11 requirement
Date: Sat, 29 Oct 2016 15:35:00 -0000 [thread overview]
Message-ID: <07c20dd3-005f-8ab8-6ad5-7d840e8f88e6@redhat.com> (raw)
In-Reply-To: <838tt7qiky.fsf@gnu.org>
On 10/29/2016 04:29 PM, Eli Zaretskii wrote:
>> 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.
>
Alright, pushed this in then.
From e6485aafde098bf182b46cb187d8fd049f309e29 Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Sat, 29 Oct 2016 16:30:34 +0100
Subject: [PATCH] gdb/NEWS: Clarify C++ requirement
gdb/ChangeLog:
2016-10-29 Pedro Alves <palves@redhat.com>
* NEWS: Clarify C++ requirement.
---
gdb/ChangeLog | 4 ++++
gdb/NEWS | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index b4a6e23..c38c65c 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,9 @@
2016-10-29 Pedro Alves <palves@redhat.com>
+ * NEWS: Clarify C++ requirement.
+
+2016-10-29 Pedro Alves <palves@redhat.com>
+
* NEWS: Adjust to mention C++11 requirement.
2016-10-29 Eli Zaretskii <eliz@gnu.org>
diff --git a/gdb/NEWS b/gdb/NEWS
index afb817f..a6b1282 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -3,7 +3,7 @@
*** Changes since GDB 7.12
-* GDB and GDBserver now require building with a C++11 compiler.
+* Building GDB and GDBserver now requires a C++11 compiler.
For example, GCC 4.8 or later.
--
2.5.5
next prev parent reply other threads:[~2016-10-29 15:35 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 1/2] gdb: Import AX_CXX_COMPILE_STDCXX from the GNU Autoconf Archive 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-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
2016-10-29 15:35 ` Pedro Alves [this message]
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=07c20dd3-005f-8ab8-6ad5-7d840e8f88e6@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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