From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Fix/complete option list/description in manual and in gdb --help.
Date: Sun, 06 Jun 2021 21:06:02 +0300 [thread overview]
Message-ID: <83pmwyhnqt.fsf@gnu.org> (raw)
In-Reply-To: <20210606143927.29069-1-philippe.waroquiers@skynet.be> (message from Philippe Waroquiers via Gdb-patches on Sun, 6 Jun 2021 16:39:27 +0200)
> Date: Sun, 6 Jun 2021 16:39:27 +0200
> From: Philippe Waroquiers via Gdb-patches <gdb-patches@sourceware.org>
>
> I am more used to the --long-option convention.
> => should the user manual be changed to consistently document and use
> --long-option ?
Yes, IMO. And in any case, we shouldn't use both -foo and --foo for
the same option, that is just counter-productive.
> (and just mention the alternative accepted conventions?)
I wouldn't, FWIW.
prev parent reply other threads:[~2021-06-06 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 14:39 Philippe Waroquiers
2021-06-06 16:58 ` Philippe Waroquiers
2021-06-06 18:06 ` Eli Zaretskii [this message]
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=83pmwyhnqt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).