From: Thomas Schwinge <tschwinge@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>,
Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>, ams@gnu.org
Subject: Re: eliminate deprecated_add_set_cmd
Date: Sun, 04 Jan 2009 17:36:00 -0000 [thread overview]
Message-ID: <20090104173520.GC26067@fencepost.gnu.org> (raw)
In-Reply-To: <20081231040958.GB31595@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
Hello!
Pedro, first, thanks for the heads-up.
On Wed, Dec 31, 2008 at 08:09:58AM +0400, Joel Brobecker wrote:
> For these particular commands, I think it's fine to change their name.
> I suspect only a few people would use them, and they won't have much
> trouble finding the new command (or asking here if not).
Agreed.
> I would prefer the set and show commands to be consistent, but that's
> only a very mild preference based purely on aesthetics.
Also agreed.
> > maint gnu-debug -> set debug gnu (, gnu-nat, gnu-hurd, gnu-whatever, ...)
> > show debug gnu
>
> I like this one better.
Yes, and also perhaps indeed change the name to ``debug gnu-nat'', as
that's exactly what it does.
Pedro, even if I don't expect any breakage, did you check your patch on a
GNU/Hurd system or shall I do so?
Also, I found another (doc-only) reference of `deprecated_add_set_cmd' in
`valprint.c'.
Regards,
Thomas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2009-01-04 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 1:15 Pedro Alves
2008-12-31 4:10 ` Joel Brobecker
2009-01-04 17:36 ` Thomas Schwinge [this message]
2009-01-05 19:31 ` Pedro Alves
2009-01-07 21:33 ` Pedro Alves
2009-01-09 14:09 ` Eli Zaretskii
2009-05-12 17:10 ` Pedro Alves
2009-05-14 14:37 ` Pierre Muller
2008-12-31 4:22 ` Eli Zaretskii
2008-12-31 4:28 ` 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=20090104173520.GC26067@fencepost.gnu.org \
--to=tschwinge@gnu.org \
--cc=ams@gnu.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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