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] Xen dom0 Kernel Patches

To: echo@xxxxxxxxxxxx
Subject: Re: [Xen-devel] Xen dom0 Kernel Patches
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Thu, 04 Jun 2009 08:59:19 +0200
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andrew Lyon <andrew.lyon@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 04 Jun 2009 00:00:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1244087028.7176.17.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <C64CAA50.CAF7%keir.fraser@xxxxxxxxxxxxx> <1244087028.7176.17.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2
On 06/04/09 05:43, Tim Post wrote:
On Wed, 2009-06-03 at 22:31 +0100, Keir Fraser wrote:

Yes, it doesn't have to be all pushed upstream for it to be used. It's just
a question of how big the out-of-upstream patchset is that Jeremy has to
manage. And actually there's maintenance work even with the upstreamed
patches, of course. But none of that directly matters for consumers of
Jeremy's tree.

No, of course it doesn't. The problem is, Jeremy's tree is very much a
moving target as he works to produce patches that upstream will accept.

Well, that might be fixable without too much effort. Maybe jeremy could simply branch off a stable branch for 2.6.30 before rebasing to 2.6.31-rc1? Just to have something people can pull which is not based on some -rc bleeding edge kernel? That branch wouldn't get updates, except maybe for cherry-picked bugfixes, maybe also 2.6.30.x stable patches if they apply cleanly. Development would still happen in the xen-next + xen-master branches of course.

cheers,
  Gerd


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