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/
Home Products Support Community News


Re: [Xen-devel] separate components and broken out patches

To: Magnus Damm <magnus.damm@xxxxxxxxx>
Subject: Re: [Xen-devel] separate components and broken out patches
From: Muli Ben-Yehuda <mulix@xxxxxxxxx>
Date: Tue, 04 Apr 2006 08:29:37 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 03 Apr 2006 22:30:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <aec7e5c30604032009n2cdfaac7u4f65039326dfe389@xxxxxxxxxxxxxx>
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: <aec7e5c30604032009n2cdfaac7u4f65039326dfe389@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11+cvs20060126
On Tue, Apr 04, 2006 at 12:09:53PM +0900, Magnus Damm wrote:

> So to make my kernel work easier I've hacked on breaking out code from
> the xen-unstable tree into three separate components:
> - kernel
> - hypervisor
> - tools

Just a heads up, in case you aren't aware of it, there's an hg kernel
tree that's cloned from the upstream kernel that you can use to work
on the kernel in the comfort of ... an hg tree. I use it for all of my
Xe  kernel work and it's infinitely better (for me) than the
sparse/patches combination. The tree is at

Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>