From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>, Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] qemu-doc: Rework the network options chapter to make "-net" less prominent
Date: Tue, 17 Apr 2018 15:20:50 +0100 [thread overview]
Message-ID: <20180417142050.GG15421@redhat.com> (raw)
In-Reply-To: <21d78c43-a6d9-95d8-ff3e-f80a9ce6b0c0@redhat.com>
On Tue, Apr 17, 2018 at 04:14:02PM +0200, Paolo Bonzini wrote:
> On 17/04/2018 16:05, Daniel P. Berrangé wrote:
> >> For what it's worth, my "[RFC PATCH 00/32] Command line QAPIfication"
> >> replaces the original parsing art by getopt_long_only().
> >>
> >> Completing that work will take some time, but once it's done, we can
> >> (and I think we should) prefer double-dash for consistency.
> > Since our existing parser accepts single & double-dash already, is it
> > worth explicitly deprecating single-dash usage right now. So that when
> > your code comes along ready to merge, we're already able to say
> > "i told you so" and drop single-dash support at that same time.
>
> Serious questions: is _anyone_ of you actually using double-dash support
> in daily invocations of QEMU?
I rarely invoke QEMU myself, usually just let libvirt do it. So mostly
i just using qemu-img/nbd/etc which expect double-dash. I didn't actually
know QEMU supported double-dash until a year or so ago.
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:[~2018-04-17 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 7:27 [Qemu-devel] [PATCH v2] qemu-doc: Rework the network options chapter to make "-net" less prominent Thomas Huth
2018-03-12 9:07 ` Paolo Bonzini
2018-03-12 12:06 ` Thomas Huth
2018-03-12 12:18 ` Eric Blake
2018-03-12 12:44 ` Paolo Bonzini
2018-03-12 13:33 ` Thomas Huth
2018-04-17 13:56 ` Markus Armbruster
2018-04-17 14:05 ` Daniel P. Berrangé
2018-04-17 14:14 ` Paolo Bonzini
2018-04-17 14:20 ` Daniel P. Berrangé [this message]
2018-04-17 14:32 ` Markus Armbruster
2018-04-17 15:01 ` Daniel P. Berrangé
2018-04-17 16:52 ` Thomas Huth
2018-04-17 16:56 ` Paolo Bonzini
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=20180417142050.GG15421@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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.