Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: philippe.waroquiers@skynet.be, gdb-patches@sourceware.org
Subject: Re: NEWS entry for Changes to the "frame", "select-frame" ...
Date: Sun, 06 Jan 2019 15:28:00 -0000	[thread overview]
Message-ID: <831s5p24bz.fsf@gnu.org> (raw)
In-Reply-To: <20190106104636.GQ3456@embecosm.com> (message from Andrew Burgess	on Sun, 6 Jan 2019 10:46:36 +0000)

> Date: Sun, 6 Jan 2019 10:46:36 +0000
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: gdb-patches <gdb-patches@sourceware.org>
> 
> * Philippe Waroquiers <philippe.waroquiers@skynet.be> [2019-01-04 21:34:31 +0100]:
> 
> > The below paragraph is at an unusual place in NEWS,
> > as new and changed commands are normally documented in the sections
> >   * New commands 
> > or
> >   * Changed commands.
> > 
> > Maybe it should be reworded and moved to these 2 sections ?
> > 
> > Philippe
> > 
> > * Changes to the "frame", "select-frame", and "info frame" CLI
> >   commands.  These commands all now take a frame specification which
> >   is either a frame level, or one of the keywords 'level', 'address',
> >   'function', or 'view' followed by a parameter.  Selecting a frame by
> >   address, or viewing a frame outside the current backtrace now
> >   requires the use of a keyword.  Selecting a frame by level is
> >   unchanged.  The MI comment "-stack-select-frame" is unchanged.
> 
> This is fine with me (as the original author), but you'll need a
> maintainer to OK the change too.

I'm OK with moving this to the "Changed commands" section.

Thanks.


  reply	other threads:[~2019-01-06 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 20:34 Philippe Waroquiers
2019-01-06 10:46 ` Andrew Burgess
2019-01-06 15:28   ` Eli Zaretskii [this message]
2019-01-09 21:41     ` Philippe Waroquiers

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=831s5p24bz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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