public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Cc: luis.machado@linaro.org, ssbssa@yahoo.de, tdevries@suse.de,
	 simon.marchi@polymtl.ca, tankut.baris.aktemur@intel.com,
	 bernd.edlinger@hotmail.de
Subject: Re: GDB 11.1 release prep update (2021-07-24)
Date: Sat, 31 Jul 2021 12:59:08 +0200	[thread overview]
Message-ID: <8bb38d28057cd3389e2cf4dd71340ad78e2f6ff3.camel@skynet.be> (raw)
In-Reply-To: <20210724211914.GA2299597@adacore.com>

On Sat, 2021-07-24 at 14:19 -0700, Joel Brobecker wrote:
> 
>   * [PhilippeW] Fix/complete option list/description in manual and in gdb --help
> 
>     RFA v2 (2021-06-20):
>         [RFAV2] Fix/complete option list/description in manual and in gdb --help.
>         https://sourceware.org/pipermail/gdb-patches/2021-June/180186.html
> 
For this, I think RFA v2 handles all review comments of Pedro and Eli
(but it has to be re-reviewed).

There is for sure a remaining question:
  which option layout should be considered as the "canonical" one 
  and so used both in the manual and in the --help output ?

As a reminder of the discussion:
  * The current gdb --help  output favours mostly  --option=VALUE description
  * The current user manual has a mix, mostly -option VALUE
    (and some are using both conventions such as -interpreter VALUE description
     using --interpreter=mi3 in the explanation text).
  * Eli preference is to use --option=VALUE
  * Pedro preference is to use -option VALUE

The patch currently uses --option=VALUE.

Thanks
Philippe



  parent reply	other threads:[~2021-07-31 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 21:19 Joel Brobecker
2021-07-26  6:52 ` Aktemur, Tankut Baris
2021-07-31 10:59 ` Philippe Waroquiers [this message]
2021-08-01 23:19   ` Joel Brobecker

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=8bb38d28057cd3389e2cf4dd71340ad78e2f6ff3.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=bernd.edlinger@hotmail.de \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=ssbssa@yahoo.de \
    --cc=tankut.baris.aktemur@intel.com \
    --cc=tdevries@suse.de \
    /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).