From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Eric Blake <eblake@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 8/8] qemu-doc: Make "-net" less prominent
Date: Tue, 20 Feb 2018 19:37:22 +0100 [thread overview]
Message-ID: <55a10378-b99f-f73c-3162-55dcf023453b@redhat.com> (raw)
In-Reply-To: <1519148406-15006-9-git-send-email-thuth@redhat.com>
On 20/02/2018 18:40, 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. And the examples are changed to use the "--device" and
> "--netdev" options instead of "-net nic -net <backend>".
Do we want to change them to "-nic" instead? The proof is in the
pudding, they say, :) and "-nic" is way easier to learn than "-device
-netdev".
And maybe we *should* go the extra mile and deprecate "-net" altogether.
The only case where the newer syntax is a bit more uncomfortable is for
"-net nic -net nic -net tap|user", which however does work with "-nic
hubport -nic hubport -netdev tap|user,id=x -netdev hubport,netdev=x".
For now I suggest dropping this patch.
Paolo
next prev parent reply other threads:[~2018-02-20 18:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 17:39 [Qemu-devel] [PATCH v2 0/8] Improvements and clean-ups related to -net Thomas Huth
2018-02-20 17:39 ` [Qemu-devel] [PATCH v2 1/8] net: Move error reporting from net_init_client/netdev to the calling site Thomas Huth
2018-02-20 17:40 ` [Qemu-devel] [PATCH v2 2/8] net: List available netdevs with "-netdev help" Thomas Huth
2018-02-20 22:28 ` Eric Blake
2018-02-20 17:40 ` [Qemu-devel] [PATCH v2 3/8] net: Only show vhost-user in the help text if CONFIG_POSIX is defined Thomas Huth
2018-02-20 17:40 ` [Qemu-devel] [PATCH v2 4/8] net: Make net_client_init() static Thomas Huth
2018-02-20 17:40 ` [Qemu-devel] [PATCH v2 5/8] net: Remove the deprecated way of dumping network packets Thomas Huth
2018-02-20 22:35 ` Eric Blake
2018-02-21 0:20 ` Thomas Huth
2018-02-20 17:40 ` [Qemu-devel] [PATCH v2 6/8] net: Remove the deprecated 'host_net_add' and 'host_net_remove' HMP commands Thomas Huth
2018-02-20 17:40 ` [Qemu-devel] [PATCH v2 7/8] net: Add a new convenience option "--nic" to configure default/on-board NICs Thomas Huth
2018-02-20 18:37 ` Paolo Bonzini
2018-02-20 17:40 ` [Qemu-devel] [PATCH v2 8/8] qemu-doc: Make "-net" less prominent Thomas Huth
2018-02-20 18:37 ` Paolo Bonzini [this message]
2018-02-21 0:05 ` Thomas Huth
2018-02-21 9:12 ` 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=55a10378-b99f-f73c-3162-55dcf023453b@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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 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).