From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Claudio Fontana" <cfontana@suse.de>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"Akihiko Odaki" <akihiko.odaki@gmail.com>,
qemu-devel@nongnu.org,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: [PATCH] audio: add help option (?) for -audiodev
Date: Wed, 7 Sep 2022 16:22:24 +0100 [thread overview]
Message-ID: <Yxi3MOT/s8nn45zp@redhat.com> (raw)
In-Reply-To: <87fsh3usub.fsf@pond.sub.org>
On Wed, Sep 07, 2022 at 05:06:36PM +0200, Markus Armbruster wrote:
> Claudio Fontana <cfontana@suse.de> writes:
>
> > add a simple help option for -audiodev, so users can do
> >
> > qemu -audiodev ?
>
> The preferred form is actually '-audiodev help'. The other one is
> deprecated. Recommend to stay away from it even in commit messages.
We introduced 'help' many many years ago, but don't thing we
ever formally deprecated '?'. Should we do so and aim to
remove it, or are we happy to keep '?' forever, despite it
tripping up shell filename expansion with single char filenames.
(tangential to this patch, NOT a request to fix something in v2)
> >
> > to get the list of drivers available.
> >
> > Signed-off-by: Claudio Fontana <cfontana@suse.de>
> > ---
> > audio/audio.c | 20 ++++++++++++++++++++
> > 1 file changed, 20 insertions(+)
Update qemu-options.hx ?
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-09-07 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 14:23 [PATCH] audio: add help option (?) for -audiodev Claudio Fontana
2022-09-07 15:06 ` Markus Armbruster
2022-09-07 15:22 ` Daniel P. Berrangé [this message]
2022-09-07 16:07 ` BALATON Zoltan
2022-09-08 5:20 ` Markus Armbruster
2022-09-07 15:56 ` Claudio Fontana
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=Yxi3MOT/s8nn45zp@redhat.com \
--to=berrange@redhat.com \
--cc=akihiko.odaki@gmail.com \
--cc=armbru@redhat.com \
--cc=cfontana@suse.de \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=richard.henderson@linaro.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.