From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LA569-0007Ct-U0 for qemu-devel@nongnu.org; Tue, 09 Dec 2008 11:06:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LA568-0007CO-G9 for qemu-devel@nongnu.org; Tue, 09 Dec 2008 11:06:09 -0500 Received: from [199.232.76.173] (port=59313 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LA568-0007CK-8h for qemu-devel@nongnu.org; Tue, 09 Dec 2008 11:06:08 -0500 Received: from yw-out-1718.google.com ([74.125.46.153]:64013) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LA567-0002o9-MP for qemu-devel@nongnu.org; Tue, 09 Dec 2008 11:06:07 -0500 Received: by yw-out-1718.google.com with SMTP id 6so11424ywa.82 for ; Tue, 09 Dec 2008 08:06:06 -0800 (PST) Message-ID: <493E9769.7030701@codemonkey.ws> Date: Tue, 09 Dec 2008 10:06:01 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] rename vlan to vnet and mark vlan as deprecated References: <20081209153727.GT15102@redhat.com> <493E92DA.2030209@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Gildas wrote: >> Introducing an alias for something as core as vlan support is not all that >> useful. We're never going to implement the vlan option. >> >> All of the internal references are for vlan too. >> >> Regards, >> >> Anthony Liguori >> > > I think that keeping backward compatibility is a good idea and I'm ok > to remove the warning message even though I don't think it does any > harm. I will modify the patch to document the fact that vlan= is not > IEEE 902.1q and that vnet= is the prefered option. > If we're going to switch to vnet= (and I don't think we should), then it should be with a flag day. And all at once conversion that changes internal and external references. > I really think that it's a change that should done, both in the code > and usage as both will greatly benefit from a move to VNET. Just look > at the actual naming mess in e1000.c where real 802.1q handling takes > place as well... > I think this may cause minor confusion for a very small number of people, but for most people, who probably have no idea what 802.1q is, it never is an issue. This is only the second time I've seen someone get confused by vlan= since the syntax was introduced. It's really not a big deal AFAICT. Regards, Anthony Liguori > Regards, > Gildas > > >