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] [FW: FYI: The plan for Xen kernels in Fedora 9]

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] [FW: FYI: The plan for Xen kernels in Fedora 9]
From: "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Date: Mon, 10 Dec 2007 17:38:26 +0000
Cc: Stephen Tweedie <sct@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Dec 2007 10:08:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1197306414.12267.23.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/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: <20071210152025.GF12703@xxxxxxxxxx> <1197306414.12267.23.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

On Mon, 2007-12-10 at 17:06 +0000, Stephen C. Tweedie wrote:

> I just tidied up my current tree, and I've pushed patches to 
> 
>       http://people.redhat.com/sct/patches/dom0-pvops/2.6.24-rc4-A0/

btw, I'm maintaining this myself as a local git repository, with two
active branches: one working branch which I'll be rebasing regularly to
keep it synced up and patched against Linus' latest tree, and which will
be getting commits reordered and merged to keep things as a sane linear
patch queue against Linus's tree; and a full-history branch, which
contains all the history of the rebases for sanity checking.

This setup works extremely well for me, but I'm not sure how useful it
is for other folks.  Because it is regularly rebased, the active branch
isn't useful as a git merge source; and because it keeps all the
historical cruft that is being pruned from the active branch, the
history branch isn't all that useful as a development base.

But I'll push these to a public git repo if anybody is interested in
using the tree in that form.  (Just as long as I can put up a big hazard
warning about the dangers of using a git tree that loses history!)

--Stephen



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