Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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:18:00 -0000	[thread overview]
Message-ID: <10b3ff78-b007-9088-ee8c-c3282df1c0b4@redhat.com> (raw)
In-Reply-To: <83wpgrr8ci.fsf@gnu.org>

On 10/29/2016 07:13 AM, Eli Zaretskii wrote:
>> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>> From: Pedro Alves <palves@redhat.com>
>> Date: Fri, 28 Oct 2016 18:17:44 +0100
>>
>> On 10/28/2016 04:08 PM, Pedro Alves wrote:
>>> On 10/28/2016 01:07 PM, Yao Qi wrote:
>>
>>>> This series is good to me.
>>>
>>> Thanks!  I've pushed it in now.  I'll send a NEWS change soon.
>>
>> Maybe this is sufficient?
> 
> Fine with me.
> 

Thanks I've pushed it in.

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.

I realized that what I had written originally may be ambiguous
with saying that we require building inferiors/debuggees
with C++11.  Reading the paragraph below clears it up, but ...

Thanks,
Pedro Alves


  reply	other threads:[~2016-10-29 15:18 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 [this message]
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=10b3ff78-b007-9088-ee8c-c3282df1c0b4@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