qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qemu-doc: Rework the network options chapter to make "-net" less prominent
Date: Tue, 17 Apr 2018 18:52:20 +0200	[thread overview]
Message-ID: <8c20b01d-d756-d251-268c-f8df14a9b8c4@redhat.com> (raw)
In-Reply-To: <87po2x6gz1.fsf@dusky.pond.sub.org>

On 17.04.2018 16:32, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
> 
>> 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 use both.  I readily concede that people familiar with QEMU probably
> use single dash a lot more than double dash.  I don't think we should
> get rid of single dash, unless we decide to bite the bullet and clean up
> our command line without regard for backward compatibility, as Thomas
> proposed elsewhere in this thread, and others proposed before, multiple
> times.

/me sings the QEMU version 3.0 blues ...

;-)

  parent reply	other threads:[~2018-04-17 16:52 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é
2018-04-17 14:32           ` Markus Armbruster
2018-04-17 15:01             ` Daniel P. Berrangé
2018-04-17 16:52             ` Thomas Huth [this message]
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=8c20b01d-d756-d251-268c-f8df14a9b8c4@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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).