Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA v2/code+DOCO+NEWS] new "set/show serial baud" command
Date: Thu, 10 Oct 2013 16:06:00 -0000	[thread overview]
Message-ID: <83vc15p0uv.fsf@gnu.org> (raw)
In-Reply-To: <20131010055928.GN3092@adacore.com>

> Date: Thu, 10 Oct 2013 09:59:28 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: palves@redhat.com, gdb-patches@sourceware.org
> 
> > > gdb/doc/ChangeLog:
> > > 
> > >         * gdb.texinfo: Replace "set remotebaud" and "show remotebaud"
> > >         by "set serial baud" and "show serial baud" (resp) throughout.
> > 
> > You didn't mention the node name in the log entry.
> 
> That was intentional, because it's a global search and replace.
> It's allowed by the GCS, but if you still prefer I repeat the node
> names, let me know, and I will dig them out.

Yes, I do prefer naming the nodes.  This makes it easier to search for
changes that modified a given node.

> > >  If you're using a serial line, you may want to give @value{GDBN} the
> > > -@w{@samp{--baud}} option, or use the @code{set remotebaud} command
> > > -(@pxref{Remote Configuration, set remotebaud}) before the
> > > +@w{@samp{--baud}} option, or use the @code{set serial baud} command
> > 
> > Is @w really needed here?  You have only one word there anyway.
> > 
> > Otherwise, OK for the documentation parts.
> 
> Thanks! For @w, now that I know what it means :-), I agree it does
> seem useless. But it was there before, so in the spirit of not
> mixing independent changes in the same patch, here is a second one
> that removes it.

Great, thanks.


  reply	other threads:[~2013-10-10 16:06 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 [this message]
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
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=83vc15p0uv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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