[Xen-devel] Re: pvops branch for new features

To:	Dulloor <dulloor@xxxxxxxxx>
Subject:	[Xen-devel] Re: pvops branch for new features
From:	Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date:	Mon, 07 Jun 2010 09:55:48 -0700
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Mon, 07 Jun 2010 09:56:37 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<AANLkTikHJvLb6c7H4jApwK_SnawY_Qst_1Iq5fnzRBZP@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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References:	<AANLkTikHJvLb6c7H4jApwK_SnawY_Qst_1Iq5fnzRBZP@xxxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4

On 06/07/2010 08:39 AM, Dulloor wrote:
> Which pvops branch should we use for new features which might not have
> many problems merging upstream (such as PV NUMA) ?
>   

If you can base your work on a stock kernel version (v2.6.34, .35-rc,
etc), then that would be preferred.  That means you can upstream it
without having to worry about dependencies on the other xen.git branches.

If your work depends on something in xen.git but not yet upstream, then
try to create a new branch with the bare minimum number of dependencies.

    J

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Re: pvops branch for new features