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


[Xen-devel] Re: master branch of xen.git

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: [Xen-devel] Re: master branch of xen.git
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 10 Aug 2010 23:45:09 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 10 Aug 2010 23:45:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C626189020000780000F382@xxxxxxxxxxxxxxxxxx>
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: <4C626189020000780000F382@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100720 Fedora/3.1.1-1.fc13 Lightning/1.0b2pre Thunderbird/3.1.1
 On 08/10/2010 11:38 PM, Jan Beulich wrote:
what's the disposition of the master branch of that tree? It doesn't
seem to have seen any update during the last couple of months,
and it's still 2.6.31-based. Shouldn't this be either what "stable"
is currently (i.e. 2.6.32-based) or match up with Linus' tree (or
the latest released version thereof)?

I keep forgetting to update it. I think of it as a deprecated branch I'd like to get rid of, since the name is too vague. In principle the name could be better used for something like "bleeding edge head", but I think changing its meaning like that would be way too much trouble, so just dropping it after migrating everything away from it is probably the best thing to do.

In the meantime, I'll make it the same as xen/stable-2.6.31.x, since that's more or less what it means. (Likewise, xen/stable is tracking xen/stable-2.6.32.x at the moment).

I've also just started putting together a (pre-rc)2.6.36-based dom0 branch which will become the development focus soon (leaving 2.6.32 still supported but with backported changes, rather than the current flow of developing in .32 then forward-porting).


Xen-devel mailing list

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