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] Unable to boot dom0 with 2.6.16-rc1 and xen-3.0-testing

To: Travis Cross <travis@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Unable to boot dom0 with 2.6.16-rc1 and xen-3.0-testing
From: Christian Limpach <christian.limpach@xxxxxxxxx>
Date: Wed, 8 Feb 2006 20:48:18 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 08 Feb 2006 20:59:25 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KKZb28/8tTPK/H3jSJWsg3DBtSQj+5M/M8+OxTYTdNj+2gy8LWFec0hijwUratzC4ry/bADSq+HrxXdhoEg8q8TWJdbpr0jFxyygtyJGlhCzuwtY8itgcqZmIRg2V3gnen9qJNChCnAM89iJKAYJYGFcyyijYMSF8sRh3FiLIEE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43EA56B8.40306@xxxxxxxxxxxxxxxxx>
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: <43E51DE7.9040009@xxxxxxxxxxxxxxxxx> <c8b29730a643d3eb01fa6d8b4aaa82de@xxxxxxxxxxxx> <43E64DD6.9060102@xxxxxxxxxxxxxxxxx> <b3f700a4d1780b9f4483ab6f6540e76b@xxxxxxxxxxxx> <43EA56B8.40306@xxxxxxxxxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 2/8/06, Travis Cross <travis@xxxxxxxxxxxxxxxxx> wrote:
> Just curious, what is the branch philosophy on the linux-2.6-xen.hg
> tree?  It appears to pull more recent changes than the testing tree,
> but not pull all the latest changes in the unstable tree.

linux-2.6-xen.hg should be ahead of xen-unstable.hg as far as tracking
linux changes is concerned -- this wasn't the case since the end of
last week because the mercurial repository on kernel.org wasn't being
updated.  I'm planing to update linux-2.6-xen.hg whenever there is a
new -rc version and then update the sparse tree if the -rc version
tests ok.

Changes we make get checked into xen-unstable first and then get
pulled across to linux-2.6-xen.hg within a day or two.


Xen-devel mailing list