qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: "open list:Block layer core" <qemu-block@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>, QEMU <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/5] option: Make option help nicer to read
Date: Fri, 19 Oct 2018 11:59:26 +0200	[thread overview]
Message-ID: <bcedefc0-e29e-02f8-f450-3b955b677636@redhat.com> (raw)
In-Reply-To: <CAJ+F1CJtT6u6ejLwmTTRWz96c6QW13pZVMF1+hTLXxD1qeV1XQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

On 16.10.18 08:46, Marc-André Lureau wrote:
> Hi
> 
> On Mon, Oct 15, 2018 at 9:34 PM Max Reitz <mreitz@redhat.com> wrote:
>>
>> This adds some whitespace into the option help (including indentation)
>> and replaces '=' by ': ' (not least because '=' should be used for
>> values, not types).
> 
> Without strong preference, I like the '=' better: it's the expected
> syntax for the command line argument. (also, --help and man pages
> describe options with "foo=type", not "foo: type")

Define "strong".  I do believe that types are different from values, and
that '=' is reserved for values and never used with types.

It's not like I'll die when we keep '=', though, but it's definitely not
what I'd use.  Maybe "foo=<str>", but that feels overly cluttered when
compared to "foo: str".  (Especially when it comes to things like
"iothread=<link<iothread>>".)

>> Furthermore, the list name is no longer printed as
>> part of every line, but only once in advance, and only if the caller did
>> not print a caption already.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
> 
> looks good to me otherwise

Well, if '=' is the only trouble, that's good. :-)

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-10-19  9:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 17:28 [Qemu-devel] [PATCH 0/5] Various option help readability improvement suggestions Max Reitz
2018-10-15 17:28 ` [Qemu-devel] [PATCH 1/5] option: Make option help nicer to read Max Reitz
2018-10-16  6:46   ` Marc-André Lureau
2018-10-19  9:59     ` Max Reitz [this message]
2018-10-16 12:12   ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2018-10-19 10:00     ` Max Reitz
2018-10-17  6:50   ` [Qemu-devel] " Markus Armbruster
2018-10-19 10:00     ` Max Reitz
2018-10-15 17:28 ` [Qemu-devel] [PATCH 2/5] chardev: Indent list of chardevs Max Reitz
2018-10-15 17:28 ` [Qemu-devel] [PATCH 3/5] qdev-monitor: Make device options help nicer Max Reitz
2018-10-15 17:28 ` [Qemu-devel] [PATCH 4/5] object: Make option help nicer to read Max Reitz
2018-10-15 17:28 ` [Qemu-devel] [PATCH 5/5] fw_cfg: Drop newline in @file description Max Reitz
2018-10-15 22:31   ` Philippe Mathieu-Daudé

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=bcedefc0-e29e-02f8-f450-3b955b677636@redhat.com \
    --to=mreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).