Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] [doc patch] gdbserver.1: Document all the options and --multi
Date: Sat, 06 Apr 2013 19:26:00 -0000	[thread overview]
Message-ID: <838v4wdmyp.fsf@gnu.org> (raw)
In-Reply-To: <20130406090127.GA8842@host2.jankratochvil.net>

> Date: Sat, 6 Apr 2013 11:01:27 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
> 
> On Sat, 06 Apr 2013 10:44:55 +0200, Eli Zaretskii wrote:
> > > I do not think it would be good, (1) the --multi mode is IMO an unusual one,
> > > a special case and (2) I also tried to generally keep the "gdbserver --help"
> > > output order.
> > 
> > Then let me suggest something specific:
> 
> That is most readable, thanks for the work.
> 
> Checked in.

Thanks.

When formatted, the generated man pages have something weird on their
last line:

  gdb-                              2013-04-06                      GDB(1)

It seems to come from this line in gdb.1:

.TH GDB 1 "2013-04-06" "gdb-" "GNU Development Tools"

Is that "gdb-" part due to some local problem on my system?  (I
produced the man pages without running configure, using Makefile.in,
so perhaps that screws up the results.)


  reply	other threads:[~2013-04-06  9:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 19:33 Jan Kratochvil
2013-04-05 20:01 ` Eli Zaretskii
2013-04-06  9:31   ` Jan Kratochvil
2013-04-06 13:56     ` Eli Zaretskii
2013-04-06 15:04       ` Jan Kratochvil
2013-04-06 15:49         ` Eli Zaretskii
2013-04-06 15:52           ` [commit] " Jan Kratochvil
2013-04-06 19:26             ` Eli Zaretskii [this message]
2013-04-06 21:45               ` Jan Kratochvil
2013-04-07  6:21                 ` [commit#2] " Jan Kratochvil

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=838v4wdmyp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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