From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kamala Narasimhan <kamala.narasimhan@gmail.com>
Subject: Re: [PATCH] xl: Special case tap/aio for disk validation
Date: Thu, 27 Jan 2011 15:14:19 -0500
Message-ID: <4D41D21B.3090400@gmail.com>
References: <4D407A06.1050902@gmail.com>
	<alpine.DEB.2.00.1101271506410.7277@kaball-desktop>
	<19777.36262.691401.791181@mariner.uk.xensource.com>
	<1296142527.14780.6892.camel@zakaz.uk.xensource.com>
	<19777.39923.755279.143976@mariner.uk.xensource.com>
	<4D41AF8C.50207@gmail.com>
	<alpine.DEB.2.00.1101271755420.7277@kaball-desktop>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <alpine.DEB.2.00.1101271755420.7277@kaball-desktop>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "Kamala Narasimhan (3P)" <kamala.narasimhan@citrix.com>
List-Id: xen-devel@lists.xenproject.org

> While fixing the disk parsing is critical for 4.1, I am not sure if we
> can deprecate the current syntax for 4.1 as well.
> We should keep in mind that xend is still using the other syntax and it
> is still present in-tree, so if we really want to deprecate it we need
> to fix xend too. 

By deprecating I didn't mean we would remove the functionality and introduce inconsistency between xend and xl in terms of usage.  I wasn't sure if we should stop with documenting the fact that it is deprecated or also display a warning message (in libxl) to that effect.  I would go with a warning also unless someone disapproves.

Kamala