From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>,
Yurij Grechishhev <yurij.grechishhev@gmail.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFA/code+NEWS] new "set/show serial baud" command (was: "Re: Setting parity for remote serial")
Date: Wed, 09 Oct 2013 02:05:00 -0000 [thread overview]
Message-ID: <CADPb22QG-WspW7mcNcV96S5ebpiL9iMePs=OSudZP5MzLaqzkA@mail.gmail.com> (raw)
In-Reply-To: <20131008141639.GF3092@adacore.com>
On Tue, Oct 8, 2013 at 7:16 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> > I'd rather we do it right the first time. If we're a go with
>> > the "set serial baud" command, I don't mind taking care of
>> > that part. As Pedro hints, it's a fairly easy change to make.
>> >
>> > Pedro, should we go ahead? It's only been a day or two, but we haven't
>> > had any objection so far.
>>
>> Yeah, I think so.
>
> Attached is a patch that implements that.
>
> gdb/ChangeLog:
>
> * cli/cli-cmds.c (show_baud_rate): Moved to serial.c as
> serial_baud_show_cmd.
> (_initialize_cli_cmds): Delete the code creating the
> "set/show remotebaud" commands.
> * serial.c (baud_rate): Move here from top.c.
> (serial_baud_show_cmd): Move here from cli/cli-cmds.c.
> (_initialize_serial): Create "set/show serial baud" commands.
> Add "set/show remotebaud" command aliases.
> * top.c (baud_rate): Moved to serial.c.
> * NEWS: Document the new "set/show serial baud" commands,
> replacing "set/show remotebaud".
>
> Tested on x86_64-linux, with no regression (I almost expected one,
> as we used to test thhe output "help set", or soemthing like that).
>
> OK to commit?
>
> Thanks,
> --
> Joel
+ /* The commands "set/show serial baud" used to have a different name.
+ Add aliases to those names to facilitate the transition. */
+ add_alias_cmd ("remotebaud", "serial baud", no_class, 0, &setlist);
+ add_alias_cmd ("remotebaud", "serial baud", no_class, 0, &showlist);
Does the mark-as-deprecated machinery work here?
next prev parent reply other threads:[~2013-10-09 2:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 15:18 Setting parity for remote serial Yurij Grechishhev
2013-07-10 18:10 ` Tom Tromey
[not found] ` <524ECCBB.5050307@gmail.com>
2013-10-07 18:33 ` Yurij Grechishhev
2013-10-08 3:56 ` Joel Brobecker
2013-10-08 12:03 ` Pedro Alves
2013-10-08 14:16 ` [RFA/code+NEWS] new "set/show serial baud" command (was: "Re: Setting parity for remote serial") Joel Brobecker
2013-10-08 14:34 ` [RFA/code+NEWS] new "set/show serial baud" command Pedro Alves
2013-10-08 15:00 ` Joel Brobecker
2013-10-08 15:12 ` Tom Tromey
2013-10-09 11:23 ` [RFA v2/code+DOCO+NEWS] " Joel Brobecker
2013-10-09 16:17 ` Pedro Alves
2013-10-10 5:55 ` checked in: " Joel Brobecker
2013-10-09 16:44 ` Eli Zaretskii
2013-10-10 5:59 ` Joel Brobecker
2013-10-10 16:06 ` Eli Zaretskii
2013-10-11 4:51 ` Joel Brobecker
2013-10-11 7:02 ` Eli Zaretskii
2013-10-08 15:24 ` [RFA/code+NEWS] new "set/show serial baud" command (was: "Re: Setting parity for remote serial") Eli Zaretskii
2013-10-09 2:05 ` Doug Evans [this message]
2013-10-09 3:57 ` Joel Brobecker
2013-10-09 8:31 ` [RFA/code+NEWS] new "set/show serial baud" command Pedro Alves
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='CADPb22QG-WspW7mcNcV96S5ebpiL9iMePs=OSudZP5MzLaqzkA@mail.gmail.com' \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=yurij.grechishhev@gmail.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