From: John Snow <jsnow@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
BALATON Zoltan <balaton@eik.bme.hu>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 1/2] trace: document how to specify multiple --trace patterns
Date: Wed, 13 Jan 2021 16:42:42 -0500 [thread overview]
Message-ID: <f13a4aac-2d9a-9762-2664-3e3e09376f4d@redhat.com> (raw)
In-Reply-To: <20210113094804.GA250553@stefanha-x1.localdomain>
On 1/13/21 4:48 AM, Stefan Hajnoczi wrote:
>> QEMU options are single dash with double dash accepted for compatibility but
>> help and other docs have single dash so these (and below) should be -trace.
>> (Also a bit less typing for otherwise already way too long command lines.)
> Is this documented somewhere?
>
> I was under the impression that '-' is legacy syntax and '--' is the
> preferred syntax. There are examples of '--' on the QEMU man page.
>
> Let's reach agreement, document it, and then make the documentation
> consistent.
>
> Stefan
My naive impression was that double-dash is the preferred idiom in
linuxdom in general for any multi-character option.
We might hang on to single-dash for backwards compatibility, but I doubt
we want to enshrine that as our preferred way.
Is there a reasoning I am unaware of?
next prev parent reply other threads:[~2021-01-13 21:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:58 [PATCH 0/2] trace: documentation improvements Stefan Hajnoczi
2021-01-12 16:58 ` [PATCH 1/2] trace: document how to specify multiple --trace patterns Stefan Hajnoczi
2021-01-12 18:50 ` Philippe Mathieu-Daudé
2021-01-12 20:44 ` BALATON Zoltan
2021-01-13 9:48 ` Stefan Hajnoczi
[not found] ` <afd6945e-2666-1b80-70c8-27564cf5ac5@eik.bme.hu>
2021-01-13 14:15 ` Stefan Hajnoczi
2021-02-15 11:39 ` Kevin Wolf
2021-01-13 21:42 ` John Snow [this message]
2021-01-13 22:15 ` Eric Blake
2021-01-13 23:08 ` John Snow
2021-01-13 23:45 ` BALATON Zoltan
2021-01-14 0:20 ` John Snow
2021-01-14 14:02 ` Stefan Hajnoczi
2021-01-14 14:18 ` BALATON Zoltan
2021-01-14 16:44 ` Stefan Hajnoczi
2021-01-19 16:31 ` Eric Blake
2021-02-01 11:22 ` Stefan Hajnoczi
2021-01-14 17:22 ` John Snow
2021-01-12 16:58 ` [PATCH 2/2] trace: update docs with meson build information Stefan Hajnoczi
2021-02-01 11:23 ` [PATCH 0/2] trace: documentation improvements Stefan Hajnoczi
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=f13a4aac-2d9a-9762-2664-3e3e09376f4d@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).