From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] qemu-doc: Rework the network options chapter to make "-net" less prominent
Date: Mon, 12 Mar 2018 14:33:16 +0100 [thread overview]
Message-ID: <47d9f2ab-b9b4-4184-4a39-d5eb73e66996@redhat.com> (raw)
In-Reply-To: <bc5f376b-ee95-5ce9-8c7c-32e75df97ec3@redhat.com>
On 12.03.2018 13:44, Paolo Bonzini wrote:
> On 12/03/2018 13:18, Eric Blake wrote:
>> On 03/12/2018 04:07 AM, Paolo Bonzini wrote:
>>> On 12/03/2018 08:27, Thomas Huth wrote:
>>>> "-net" is clearly a legacy option. Yet we still use it in almost all
>>>> examples in the qemu documentation, and many other spots in the network
>>>> chapter. We should make it less prominent that users are not lured into
>>>> using it so often anymore. So instead of starting the network chapter
>>>> with
>>>> "-net nic" and documenting "-net <backend>" below "-netdev <backend>"
>>>> everywhere, all the "-net" related documentation is now moved to the end
>>>> of the chapter. The new "--nic" option is moved to the beginning of the
>>>> chapter instead, with a new example that should demonstrate how "--nic"
>>>> can be used to shortcut "--device" with "--netdev". The examples in this
>>>> chapter are changed to use the "--device" and "--netdev" options or
>>>> "--nic" instead of "-net nic -net <backend>".
>>>>
>>>> While we're at it, also remove a legacy remark about very old Linux
>>>> distributions. Also remove the "[...]" from the examples in this chapter
>>>> since we are not using this ellipsis in any other examples in our docu-
>>>> mentation.
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>> ---
>>>> v2:
>>>> - Fixed the bad "--device=e1000" example
>>>
>>> Frankly I think this is the proof that double-dash option names are a
>>> bad idea. The reason to do that was to make qemu-img and qemu command
>>> lines more similar in the documentation, but the truth is they are not
>>> similar and shouldn't be made similar. The equal sign is one example,
>>> where qemu-img supports "--format=raw" but QEMU doesn't support
>>> "--device=e1000", but it's not the only one.
>>
>> Our hand-rolled parser sucks. We should fix it to be more like getopt,
>> at which point --device=e1000 would work.
>
> "--device=e1000,netdev=user0" is also pretty confusing, as is
> "--machine=kernel_irqchip=off".
>
>>> qemu-img supports things such as "-fraw", qemu doesn't---for example
>>> "-m1024" doesn't work).
>>
>> Our hand-rolled parser sucks. We should fix it to be more like getopt,
>> at which point -m1024 would work.
>
> For -m1024 it makes sense, but what about -d? How do you explain that
> "-din_asm" is a short form of "-d in_asm", but "-device" is not a short
> form of "-d evice"?
Slightly off-topic, but: I think it is also quite unfortunate that we
use a short option "-d" for something that you need rather seldomly,
while something important like "-device" does not have an abbreviated
one-letter alternative.
> I agree that having a non-standard option parser is bad, but
> getopt_long_only always seemed to me like the worst of both worlds.
> "All options are 'long', cannot be abbreviated, must be separated from
> their argument" is pretty easy.
Hey, what about switching to getopt_long(), breaking with traditions and
call the first version that contains the change "QEMU v3.0"? ;-)
... SCNR.
Thomas
next prev parent reply other threads:[~2018-03-12 13:33 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 [this message]
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
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=47d9f2ab-b9b4-4184-4a39-d5eb73e66996@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@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).