From: Eric Blake <eblake@redhat.com>
To: "Emilio G. Cota" <cota@braap.org>,
Yaowei Bai <baiyaowei@cmss.chinamobile.com>
Cc: qemu-trivial@nongnu.org, mjt@tls.msk.ru, laurent@vivier.eu,
stefanha@redhat.com, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] tracing.txt: add missing '-' for trace option
Date: Wed, 13 Jun 2018 06:27:49 -0500 [thread overview]
Message-ID: <23a38716-196f-53a0-0a3d-61f269b1dab4@redhat.com> (raw)
In-Reply-To: <20180613035030.GB25430@flamenco>
On 06/12/2018 10:50 PM, Emilio G. Cota wrote:
> On Tue, Jun 12, 2018 at 23:15:49 -0400, Yaowei Bai wrote:
>> Signed-off-by: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
>> ---
>> docs/devel/tracing.txt | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/docs/devel/tracing.txt b/docs/devel/tracing.txt
>> index 07abbb3..6ab32cc 100644
>> --- a/docs/devel/tracing.txt
>> +++ b/docs/devel/tracing.txt
>> @@ -18,7 +18,7 @@ for debugging, profiling, and observing execution.
>>
>> 3. Run the virtual machine to produce a trace file:
>>
>> - qemu -trace events=/tmp/events ... # your normal QEMU invocation
>> + qemu --trace events=/tmp/events ... # your normal QEMU invocation
>
> The second dash is not missing; both '-args' and '--args' work.
>
> '-args' seems to be favoured though; see `qemu -h' or `qemu --h' :-)
Actually, we're trying to fix that:
https://wiki.qemu.org/BiteSizedTasks#Consistent_option_usage_in_documentation
The one-vs-two dash usage is only supported in qemu, not in qemu-nbd or
qemu-img (that is, qemu acts as if it uses getopt_long_only(), while the
others use getopt_long() - except that we hand-rolled the parser in
qemu, meaning you might find quirks where it sometimes doesn't even
match getopt_long_only()).
At any rate, since --trace is an option that is supported across
multiple binaries, we SHOULD favor the double-dash spelling in our
documentation, so that you can consistently reuse the same --trace
invocation without worrying whether the binary parses its arguments with
getopt_long() (where double is required) or like getopt_long_only()
(where the double is optional but supported).
So I'm in favor of this patch, although it may need more of a commit
message summarizing the justification I've just pointed you to.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-06-13 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 3:15 [Qemu-devel] [PATCH] tracing.txt: add missing '-' for trace option Yaowei Bai
2018-06-13 3:50 ` Emilio G. Cota
2018-06-13 8:44 ` Yaowei Bai
2018-06-13 11:27 ` Eric Blake [this message]
2018-06-13 14:15 ` Yaowei Bai
2018-06-15 17:30 ` Stefan Hajnoczi
2018-06-18 22:11 ` Eric Blake
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=23a38716-196f-53a0-0a3d-61f269b1dab4@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=cota@braap.org \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.com \
/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).