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 master/8.0] Fix NEWS formatting in GDB 8.0 section
Date: Sun, 28 May 2017 21:18:00 -0000	[thread overview]
Message-ID: <15815a00b8c9ae22697217c6247872b7@polymtl.ca> (raw)
In-Reply-To: <83inkpklh4.fsf@gnu.org>

On 2017-05-25 17:24, Eli Zaretskii wrote:
> Thanks for catching this.
> 
> I think we want it the other way around, though: move flash-erase
> entry to the "New commands" section that comes after "New MI
> commands", to be consistent with what we did in previous releases.

Hmm do you have an example of this?  There hasn't been new MI commands 
in a while from what I can see.

I put it this way because CLI commands are of interest to way more 
people than MI commands, so I think they should be higher in the list.  
But AFAIK, the order of NEWS is usually just the chronological order in 
which things were added (unless adding an item to an existing 
subsection), we don't follow a defined structure.

Simon


  reply	other threads:[~2017-05-28 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 12:12 Simon Marchi
2017-05-25 15:25 ` Eli Zaretskii
2017-05-28 21:18   ` Simon Marchi [this message]
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

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=15815a00b8c9ae22697217c6247872b7@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