[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Unable to boot dom0 with 2.6.16-rc1 and xen-3.0-testing

  • To: Travis Cross <travis@xxxxxxxxxxxxxxxxx>
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.