From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] For all targets and machine types: "start to monitor" smoke test
Date: Tue, 07 Aug 2012 14:37:12 -0600 [thread overview]
Message-ID: <50217C78.7070400@redhat.com> (raw)
In-Reply-To: <87hasea1ie.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
On 08/07/2012 02:30 PM, Markus Armbruster wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> On 7 August 2012 20:55, Markus Armbruster <armbru@redhat.com> wrote:
>>> Anthony Liguori <anthony@codemonkey.ws> writes:
>>>> Perhaps we could add a QEMUMachine parameter that indicates that the
>>>> machine doesn't start without special options.
>>>
>>> Recommend to make it a string that lists the mandatory options.
>>
>> How are you going to say "need either option foo or option bar" ? I'm
>> pretty sure we have some of those (eg "either you need to pass a flash
>> image or a kernel").
>
> Yes, we do.
>
> The string should be suitable for inserting into -help.
Convention in other programs' -help output is to express a mandatory
selection from mutually exclusive options using {}, as in:
{ -foo | -bar }
If both options can be used together, but cannot both be omitted, then
this style works:
{ -foo [ -bar ] | -bar }
Mutually exclusive options, but where omission is okay, would then be:
[ { -foo | -bar } ]
or even this variant, to express the default when both are omitted:
{ -foo | [ -bar ] }
Using strings with metasyntax like that should be usable in qemu -help.
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2012-08-07 20:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 19:26 [Qemu-devel] For all targets and machine types: "start to monitor" smoke test Markus Armbruster
2012-08-07 19:35 ` Anthony Liguori
2012-08-07 19:55 ` Markus Armbruster
2012-08-07 20:05 ` Peter Maydell
2012-08-07 20:30 ` Markus Armbruster
2012-08-07 20:37 ` Eric Blake [this message]
2012-08-08 7:50 ` Markus Armbruster
2012-08-08 8:03 ` Peter Maydell
2012-08-08 8:29 ` Markus Armbruster
2012-08-07 19:42 ` Peter Maydell
2012-08-08 7:22 ` Markus Armbruster
2012-08-10 1:29 ` Peter Crosthwaite
2012-08-07 20:34 ` Andreas Färber
2012-08-08 7:27 ` Markus Armbruster
2012-08-08 12:22 ` Markus Armbruster
2012-08-07 21:06 ` Blue Swirl
2012-08-08 7:39 ` Markus Armbruster
2012-08-08 19:34 ` Blue Swirl
2012-08-08 7:38 ` Max Filippov
2012-08-08 8:31 ` Markus Armbruster
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=50217C78.7070400@redhat.com \
--to=eblake@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.