Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Fix NEWS formatting in GDB 8.0 section
Date: Tue, 30 May 2017 09:37:00 -0000	[thread overview]
Message-ID: <57631a79da4d7361b7b403996352af27@polymtl.ca> (raw)
In-Reply-To: <83h902em24.fsf@gnu.org>

On 2017-05-30 11:22, Eli Zaretskii wrote:
>> From: Simon Marchi <simon.marchi@ericsson.com>
>> CC: Eli Zaretskii <eliz@gnu.org>, Simon Marchi 
>> <simon.marchi@ericsson.com>
>> Date: Tue, 30 May 2017 11:12:35 +0200
>> 
>> Change the GDB 8.0 section of the NEWS file to try to follow this 
>> order:
>> 
>>   * Functional changes
>>   * Added and removed configurations and targets
>>   * New commands
>>   * New options
>>   * MI changes
>> 
>> In particular, there were two "New commands" sections.
>> 
>> gdb/ChangeLog:
>> 
>> 	* NEWS (Changes in GDB 8.0): Remove extra empty line.  Move
>> 	"Removed targets and native configurations" up.  Merge duplicate
>> 	"New commands" sub-sections.  Add "New options" sub-sections.
> 
> Thanks, this is OK.

Thanks, pushed to both master and gdb-8.0-branch.

(Just noticed I went directly from v1 to v3, whoops)


      reply	other threads:[~2017-05-30  9:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 12:12 [PATCH master/8.0] " Simon Marchi
2017-05-25 15:25 ` Eli Zaretskii
2017-05-28 21:18   ` Simon Marchi
2017-05-29  2:35     ` Eli Zaretskii
2017-05-29  5:25       ` Simon Marchi
2017-05-30  7:35         ` Eli Zaretskii
2017-05-30  9:12           ` [PATCH v3] " Simon Marchi
2017-05-30  9:22             ` Eli Zaretskii
2017-05-30  9:37               ` Simon Marchi [this message]

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=57631a79da4d7361b7b403996352af27@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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