qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>,
	qemu-devel@nongnu.org, marcandre.lureau@gmail.com,
	eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 0/2] Improve -help
Date: Mon, 5 Oct 2015 17:32:05 +0200	[thread overview]
Message-ID: <561297F5.5010609@redhat.com> (raw)
In-Reply-To: <1442253680-8657-1-git-send-email-lvivier@redhat.com>



On 14/09/2015 20:01, Laurent Vivier wrote:
> This series allows to only display a given list of help sections.
> 
> v5: introduce "-help[=LIST]", move help of help to the end "all" section.
>     Remove typo fix (already included).
> v4: as proposed by Eric, provide a list of sections, restore default -help
> v3: add a 2nd patch to add an help section, -help displays only this section
> v2: simplify the dance of #define/#undef, thanks to Marc-André.
> 
> Laurent Vivier (2):
>   vl: Allow to define optional parameter with -arg[=params]
>   Use help sub-sections to create sub-help options
> 
>  qemu-options.hx | 124 ++++++++++++++++++++++++++++++++++--
>  vl.c            | 191 +++++++++++++++++++++++++++++++++++++++++++++++++++-----
>  2 files changed, 294 insertions(+), 21 deletions(-)
> 

The idea is great, but I think standard options really applied only to
"-help" and "-version".  Almost everything else ended up under that
heading just because no one wrote a heading...

-add-fd           expert
-audio-help       can be put into display for now
-balloon          Generic object creation (not really...)
-boot             Machine creation options?
-cpu              Machine creation options?
-device           Machine creation options?
-global           expert
-k                Display options
-machine          Machine creation options?
-m[emory]         Machine creation options?
-mem-path         Machine creation options?
-mem-prealloc     Machine creation options?
-name             expert
-numa             Machine creation options?
-set              expert
-smp              Machine creation options?
-soundhw          can be put into display for now?
-uuid             expert

Paolo

      parent reply	other threads:[~2015-10-05 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 18:01 [Qemu-devel] [PATCH v5 0/2] Improve -help Laurent Vivier
2015-09-14 18:01 ` [Qemu-devel] [PATCH v5 1/2] vl: Allow to define optional parameter with -arg[=params] Laurent Vivier
2015-09-24 16:14   ` Laurent Vivier
2015-09-14 18:01 ` [Qemu-devel] [PATCH v5 2/2] Use help sub-sections to create sub-help options Laurent Vivier
2015-09-24 16:14   ` Laurent Vivier
2015-10-05 21:00   ` Michael S. Tsirkin
2015-10-05 13:20 ` [Qemu-devel] [PATCH v5 0/2] Improve -help Laurent Vivier
2015-10-05 15:08   ` Marc-André Lureau
2015-10-05 15:17     ` Daniel P. Berrange
2015-10-05 21:08   ` Michael S. Tsirkin
2015-10-05 22:04     ` Laurent Vivier
2015-10-05 22:50       ` Michael S. Tsirkin
2015-10-05 15:32 ` Paolo Bonzini [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=561297F5.5010609@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=eblake@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --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).