From: John Snow <jsnow@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 1/2] trace: document how to specify multiple --trace patterns
Date: Wed, 13 Jan 2021 19:20:42 -0500 [thread overview]
Message-ID: <20f2dbbf-638c-4c3f-0513-0c7f1afed15d@redhat.com> (raw)
In-Reply-To: <95abf7c3-4338-1659-8c83-e4fb886794b7@eik.bme.hu>
On 1/13/21 6:45 PM, BALATON Zoltan wrote:
>
> Please don't. That would break all scripts that already call qemu using
> single dash options. Forcing everyone to edit their scripts is not nice.
> How about also accepting single dash in qemu-img for consistency then
> you can use whatever you want in docs as long as single dash still works
> for consistency and backward compatibility.
That's not what I meant -- I meant for documentation purposes. QEMU can
keep accepting single dash, but we should standardize on the spelling
for purposes of interactive messages, documentation, etc.
--js
next prev parent reply other threads:[~2021-01-14 0:22 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
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 [this message]
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=20f2dbbf-638c-4c3f-0513-0c7f1afed15d@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).