From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA v2/code+DOCO+NEWS] new "set/show serial baud" command
Date: Fri, 11 Oct 2013 04:51:00 -0000 [thread overview]
Message-ID: <20131011045155.GO3092@adacore.com> (raw)
In-Reply-To: <83vc15p0uv.fsf@gnu.org>
> Yes, I do prefer naming the nodes. This makes it easier to search for
> changes that modified a given node.
OK, that's fair enough, especially for a change of this (small) size.
Here is the new ChangeLog entry I just checked in:
* gdb.texinfo (Connecting): Replace "set remotebaud" by "set
serial baud".
(Remote Configuration): Replace "set remotebaud" by "set serial
baud". Replace "show remotebaud" by "show serial baud".
--
Joel
next prev parent reply other threads:[~2013-10-11 4:51 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 [this message]
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
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=20131011045155.GO3092@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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