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] the latest dom0 tree

To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] the latest dom0 tree
From: M A Young <m.a.young@xxxxxxxxxxxx>
Date: Mon, 20 Apr 2009 11:28:58 +0100 (BST)
Delivery-date: Mon, 20 Apr 2009 03:29:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E2263E4A5B2284449EEBD0AAB751098401D184852A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <E2263E4A5B2284449EEBD0AAB751098401D184852A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (GSO 1167 2008-08-23)
On Mon, 20 Apr 2009, Jiang, Yunhong wrote:

Hi, Jeremy, when I check the latest dom0 tree, seems the latest changeset is still in March 29 as shown below. As I'm new to git, so I want to confirm I didn't make anything wrong, and there is no changes after that? And also, all pv_dom0 work should base on xen/dom0/hackery branch, am I right?

xen/dom0/hackery was left behind a bit during the attempt to get dom0 into 2.6.30 during the merge window. Alternate branches to use are push2/xen/dom0/master and xen-tip/next . I believe the plan is that xen-tip/next will become the branch to use, but not all the patches from the other branches have been copied across yet.

        Michael Young

Xen-devel mailing list

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