From: Philippe Waroquiers via Gdb-patches <gdb-patches@sourceware.org>
To: Bruno Larsen <blarsen@redhat.com>,
Sergio Durigan Junior <sergiodj@sergiodj.net>,
Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdb/doc]: Updated manpages to be consistent with help
Date: Thu, 14 Oct 2021 20:56:05 +0200 [thread overview]
Message-ID: <97db0ebc9dedf0dd9a75ac32be57d1f689a21083.camel@skynet.be> (raw)
In-Reply-To: <8cd51cc0-3ca2-b1ae-e608-82a7cac10bcc@redhat.com>
Note that I started a patch to have the options consistently using --
But as GDB accepts various layout for options (such as -thisone or --thisone),
it was not very clear it that was a good thing to do.
Pedro e.g. commented that GDB does not use the concept of 'short' and 'long' options.
Finally, as I understand, the decision was rather to use as cannnical form
-thisone
(in the doc and on line help)
and so the manual should then also be aligned.
Sadly, I had no time to finalize the patch (i.e. to rather systematically use
the single dash convention).
But this patch seems then not to go into what I think is the last agreed direction.
See the initial RFC in
https://sourceware.org/pipermail/gdb-patches/2021-June/179587.html
and RFA in
https://sourceware.org/pipermail/gdb-patches/2021-June/179834.html
Thanks
Philippe
On Thu, 2021-10-14 at 10:10 -0300, Bruno Larsen via Gdb-patches wrote:
> On 10/13/21 12:30 PM, Sergio Durigan Junior wrote:
> > On Wednesday, October 13 2021, Bruno Larsen via Gdb-patches wrote:
> >
> > > Updated manpages to be consistent with help information provided by the
> > > binary. The main changes are Making all long-form options have '--',
> > > instead of a single '-' and added most of the missing options to the
> > > manpage.
> >
> > You might want to mention/fix
> > https://sourceware.org/bugzilla/show_bug.cgi?id=23965 and likely other
> > related manpage bugs in this commit.
> >
> > Thanks,
> >
> Good catch! I added this bug and https://sourceware.org/bugzilla/show_bug.cgi?id=10619
>
> The other ones were unrelated (documentation of ?? and reordering of options to be alphabetical)
>
next prev parent reply other threads:[~2021-10-14 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 13:04 Bruno Larsen via Gdb-patches
2021-10-13 13:50 ` Eli Zaretskii via Gdb-patches
2021-10-13 15:03 ` Bruno Larsen via Gdb-patches
2021-10-13 15:30 ` Sergio Durigan Junior via Gdb-patches
2021-10-14 13:10 ` Bruno Larsen via Gdb-patches
2021-10-14 18:56 ` Philippe Waroquiers via Gdb-patches [this message]
2021-10-15 13:27 ` Bruno Larsen via Gdb-patches
2021-10-16 11:44 ` Philippe Waroquiers via Gdb-patches
2021-10-19 13:24 ` Bruno Larsen via Gdb-patches
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=97db0ebc9dedf0dd9a75ac32be57d1f689a21083.camel@skynet.be \
--to=gdb-patches@sourceware.org \
--cc=blarsen@redhat.com \
--cc=philippe.waroquiers@skynet.be \
--cc=sergiodj@sergiodj.net \
/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