From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Armbruster Subject: Re: Has 3.0.3 been released? Date: Wed, 18 Oct 2006 14:43:25 +0200 Message-ID: <874pu1kd5e.fsf@pike.pond.sub.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: (Keir Fraser's message of "Tue, 17 Oct 2006 22:55:20 +0100") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Aron Griffis , Anthony Liguori , xen-devel List-Id: xen-devel@lists.xenproject.org Keir Fraser writes: > On 17/10/06 11:01 pm, "Aron Griffis" wrote: > >> Will xen-unstable move forward to (at least) 2.6.18 now? > > This is certainly planned before 3.0.4. Do you expect it to fall behind again during the development cycle, and how much? >> 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. Ahem. Isn't there enough suffering in the world? The sparse tree has been an enourmous pain in the neck for me and many others. If all that pain is outweighed by quicker cloning of Linux repos, then you must do that much more often than I can imagine.