qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] rename vlan to vnet and mark vlan as deprecated
Date: Tue, 9 Dec 2008 16:51:25 +0000	[thread overview]
Message-ID: <20081209165125.GU15102@redhat.com> (raw)
In-Reply-To: <493E9F79.60407@codemonkey.ws>

On Tue, Dec 09, 2008 at 10:40:25AM -0600, Anthony Liguori wrote:
> Kristoffer Ericson wrote:
> >On Tue, 09 Dec 2008 09:29:49 -0600
> >Anthony Liguori <anthony@codemonkey.ws> wrote:
> >
> >  
> >>Gildas wrote:
> >>    
> >>>Hi all,
> >>>
> >>>As I agree with the thread "vlan option is misleading, what about vnet
> >>>?" and I found sending a patch would be more constructive than a "+1",
> >>>here it is.
> >>>  
> >>>      
> >>I don't think this is a good idea.  vlan has been the option name for a 
> >>long time and changing it now will lead to quite a lot of confusion.  I 
> >>agree that it's not perhaps the best name but it's too late now to 
> >>change it.
> >>    
> >
> >I understand your point but keeping something that
> >"everyone" agrees is misleading (myself included) just
> >because it's been used in the past is silly.
> >  
> 
> I don't think everyone agrees.  I think most people haven't even weighed 
> in.  What QEMU implements is a VLAN.  The term vlan existed long before 
> 802.11q.  It is not the only way to create a VLAN, just one of the more 
> common ones today.
> 
> QEMU's usage of vlan is actually correct.

So this basically says the key failing is the documentation we have 
for the vlan= option. If people are getting confused by what QEMU
is doing and its (non-)relation to 801.11q, then we need something
to clarify this in the docs rather than changing the name of option.
Since changing the name isn't really explaining things any better

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2008-12-09 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 15:01 [Qemu-devel] [PATCH] rename vlan to vnet and mark vlan as deprecated Gildas
2008-12-09 15:29 ` Anthony Liguori
2008-12-09 17:20   ` Kristoffer Ericson
2008-12-09 16:40     ` Anthony Liguori
2008-12-09 16:51       ` Daniel P. Berrange [this message]
2008-12-09 17:14     ` Paul Brook
2008-12-09 15:37 ` Daniel P. Berrange
2008-12-09 15:46   ` Anthony Liguori
2008-12-09 15:58     ` Gildas
2008-12-09 16:06       ` Anthony Liguori
2008-12-09 16:30         ` Gildas
2008-12-09 21:36         ` Luca Bigliardi

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=20081209165125.GU15102@redhat.com \
    --to=berrange@redhat.com \
    --cc=kristoffer.ericson@gmail.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).