From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Williamson <alex.williamson@hp.com>
Subject: Re: new repo layout?
Date: Mon, 04 Jun 2007 08:39:46 -0600
Message-ID: <1180967986.6221.133.camel@bling>
References: <20070530214638.GA21589@fc.hp.com>
	<1180598644.29571.57.camel@localhost.localdomain>
	<1180627325.16734.26.camel@basalt>
	<1180628637.29571.84.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1180628637.29571.84.camel@localhost.localdomain>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/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/cgi-bin/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: Ian Campbell <Ian.Campbell@XenSource.com>
Cc: Aron Griffis <aron@hp.com>, xen-devel@lists.xensource.com, Hollis Blanchard <hollisb@us.ibm.com>
List-Id: xen-devel@lists.xenproject.org

Hi Ian,

   I see the sparse tree has been removed from staging now.  How do you
envision architecture maintained trees fit into this new build system?
For instance, I'd like for a tree cloned from xen-ia64-unstable.hg to
pull a linux-2.6.18-xen-ia64.hg tree rather than the default upstream
tree.  I see there's support for cloning linux-2.6.18-xen.hg from a
directory, but it would be quite an error prone kludge to sneak
different arch trees in that way.  Thoughts?  Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.