From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: nickrob@snap.net.nz, gdb@sourceware.org
Subject: Re: `processor' command
Date: Sat, 17 Feb 2007 21:20:00 -0000 [thread overview]
Message-ID: <20070217135311.GB28444@caradoc.them.org> (raw)
In-Reply-To: <uhctlkrtn.fsf@gnu.org>
On Sat, Feb 17, 2007 at 12:21:24PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 16 Feb 2007 07:54:43 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb@sourceware.org
> >
> > On Fri, Feb 16, 2007 at 05:05:53PM +1300, Nick Roberts wrote:
> > >
> > > The manual says:
> > >
> > > `set processor'
> > > `processor'
> > > These are alias commands for, respectively, `set architecture' and
> > > `show architecture'.
> > >
> > > The command `processor' doesn't work for me. As it's an alias anyway how about
> > > getting rid of it?
> >
> > I guess it was supposed to be "show processor"? But in any case there
> > isn't one, only "set processor" is implemented. So I think we can
> > un-document "processor".
>
> If there is `set processor', there should be also `show processor'.
> So I think we should either remove the former or add the latter.
>
> I'm not sure what you meant by ``un-document''; if that means leave a
> command, but don't document it, I'm against it.
I meant to remove the documentation for the "processor" command, which
does not exist. Maybe it did once but the command has already been
removed.
My next choice would be to remove "set processor"; but if you think
it's still in use and worthwhile as an alias, we could add
"show processor" as a new alias instead.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-17 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 12:43 Nick Roberts
2007-02-16 12:56 ` Daniel Jacobowitz
2007-02-17 11:43 ` Eli Zaretskii
2007-02-17 21:20 ` Daniel Jacobowitz [this message]
2007-02-18 10:47 ` Nick Roberts
2007-02-18 22:42 ` Eli Zaretskii
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=20070217135311.GB28444@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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