From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aron Griffis <aron@hp.com>
Subject: Re: Has 3.0.3 been released?
Date: Tue, 17 Oct 2006 18:26:40 -0400
Message-ID: <20061017222639.GE27879@fc.hp.com>
References: <20061017220124.GD27879@fc.hp.com>
	<C15B0FD8.2AFB%Keir.Fraser@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <C15B0FD8.2AFB%Keir.Fraser@cl.cam.ac.uk>
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: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Anthony Liguori <aliguori@us.ibm.com>, xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Keir Fraser wrote:  [Tue Oct 17 2006, 05:55:20PM EDT]
> > Will the tree structure change from the current sparse model to
> > a fully-populated kernel?  IMHO it wouldn't be too hard to use
> > something similar to
> > http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg plus a top-level
> > xen directory containing the hypervisor.  Alternatively, since Xen
> > isn't just Linux, maybe the hypervisor and kernels should be in
> > separate repositories?
> 
> Perhaps. We might at least separate the kernel bits from the
> hypervisor bits. We like working with a sparse tree as it's much
> quicker than cloning entire Linux repos.

I suppose xen/include/public synchronization also poses a challenge,
unless it's okay for the kernel to #include files outside of the
kernel tree.

Aron