Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>,
	ams@gnu.org, 	Thomas Schwinge <tschwinge@gnu.org>
Subject: Re: eliminate deprecated_add_set_cmd
Date: Wed, 31 Dec 2008 04:10:00 -0000	[thread overview]
Message-ID: <20081231040958.GB31595@adacore.com> (raw)
In-Reply-To: <200812310114.45103.pedro@codesourcery.com>

My 2 cents:

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).

I would prefer the set and show commands to be consistent, but that's
only a very mild preference based purely on aesthetics.


> E.g., say, for the x86 debug registers debug output,
> 
>  maint show-debug-regs -> maint set show-debug-regs on|off
>                           maint show show-debug-regs

I like this one better.

>  maint gnu-debug -> set debug gnu (, gnu-nat, gnu-hurd, gnu-whatever, ...)
>                     show debug gnu

I like this one better.

-- 
Joel


  reply	other threads:[~2008-12-31  4:10 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 [this message]
2009-01-04 17:36   ` Thomas Schwinge
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=20081231040958.GB31595@adacore.com \
    --to=brobecker@adacore.com \
    --cc=ams@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=tschwinge@gnu.org \
    /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