From: Anthony Liguori <anthony@codemonkey.ws>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rename vlan to vnet and mark vlan as deprecated
Date: Tue, 09 Dec 2008 10:40:25 -0600 [thread overview]
Message-ID: <493E9F79.60407@codemonkey.ws> (raw)
In-Reply-To: <20081209182027.37515e6e.kristoffer.ericson@gmail.com>
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.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-12-09 16:40 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 [this message]
2008-12-09 16:51 ` Daniel P. Berrange
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=493E9F79.60407@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).