WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Has 3.0.3 been released?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Has 3.0.3 been released?
From: Markus Armbruster <armbru@xxxxxxxxxx>
Date: Wed, 18 Oct 2006 14:43:25 +0200
Cc: Aron Griffis <aron@xxxxxx>, Anthony Liguori <aliguori@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 18 Oct 2006 05:43:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C15B0FD8.2AFB%Keir.Fraser@xxxxxxxxxxxx> (Keir Fraser's message of "Tue, 17 Oct 2006 22:55:20 +0100")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C15B0FD8.2AFB%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> writes:

> On 17/10/06 11:01 pm, "Aron Griffis" <aron@xxxxxx> 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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel