Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org,
	kevinb@redhat.com, macro@codesourcery.com
Subject: Re: [SH] regs command
Date: Wed, 16 May 2012 19:36:00 -0000	[thread overview]
Message-ID: <83pqa3or1f.fsf@gnu.org> (raw)
In-Reply-To: <87zk98qe8t.fsf@schwinge.name>

> From: Thomas Schwinge <thomas@codesourcery.com>
> Cc: gdb-patches@sourceware.org, Kevin Buettner <kevinb@redhat.com>, "Maciej W. Rozycki" <macro@codesourcery.com>
> Date: Wed, 16 May 2012 18:31:30 +0200
> 
> On Wed, 16 May 2012 07:26:33 -0700, Joel Brobecker <brobecker@adacore.com> wrote:
> > > I therefore propose to remove sh_show_regs_command et al. from sh-tdep.c.
> > > If nobody objects, can it just go silently, or should invoking it then
> > > cause an error message, like »Please use the »info all-registers« command
> > > instead of »regs«.«?
> > 
> > Make it an alias of "info reg" or "info all-registers", and make
> > the alias deprecated, so that users get a warning when they use it?
> > We can make that command deprecated for 7.5, and then remove it
> > from HEAD after 7.5 is branched, in a few weeks.
> 
> Sounds good, and thusly implemented, OK to commit?

The documentation parts are okay.  Thanks.


  parent reply	other threads:[~2012-05-16 19:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 13:56 Thomas Schwinge
2012-05-16 14:26 ` Joel Brobecker
2012-05-16 16:32   ` Thomas Schwinge
2012-05-16 16:58     ` Joel Brobecker
2012-05-16 17:21       ` Thomas Schwinge
2012-05-16 18:47         ` Tom Tromey
2012-05-16 19:06           ` Joel Brobecker
2012-05-16 19:38             ` Maciej W. Rozycki
2012-05-17  0:59               ` Maciej W. Rozycki
2012-05-17 11:10                 ` Mark Kettenis
2012-05-17 11:23                   ` Maciej W. Rozycki
2012-05-17 12:38                     ` Joel Brobecker
2012-05-17 15:23                       ` Mark Kettenis
2012-05-17 15:45                         ` Joel Brobecker
2012-05-17 19:52                           ` Tom Tromey
2012-05-17 20:38                             ` Joel Brobecker
2012-05-18 12:23                               ` Maciej W. Rozycki
2012-05-18 12:39                                 ` Pedro Alves
2012-05-18 12:49                                   ` Joel Brobecker
2012-05-18 13:33                                     ` Pedro Alves
2012-05-18 13:47                                 ` Tom Tromey
2012-05-21 23:36                                   ` Maciej W. Rozycki
2012-05-24 18:05                                     ` Tom Tromey
2012-05-17 19:32         ` Kevin Buettner
2012-05-16 18:36       ` Tom Tromey
2012-05-16 18:36     ` Pedro Alves
2012-05-16 19:36     ` Eli Zaretskii [this message]
2012-06-06 18:10     ` Thomas Schwinge
2012-08-10  9:22       ` Thomas Schwinge
2012-08-10 16:20         ` Tom Tromey

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=83pqa3or1f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=macro@codesourcery.com \
    --cc=thomas@codesourcery.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