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] building xen without mercury repository access

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] building xen without mercury repository access
From: "Valter Douglas Lisbôa Jr." <douglas@xxxxxxxxxxxxx>
Date: Mon, 11 Feb 2008 20:40:03 -0200
Delivery-date: Mon, 11 Feb 2008 14:40:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47B0CCFB.30709@xxxxxxxx>
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>
Organization: Trenix - IT Solutions
References: <C3D06F66.137B3%Keir.Fraser@xxxxxxxxxxxx> <47B0CCFB.30709@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.7
On Monday 11 February 2008 20:32:27 Guillaume Rousse wrote:
> Anyway, using pristine kernel source tarball is not enough. How can I
> fetch just the xen dom0 patchset against it ? cloning the whole
> linux-2.6.18-xen.hg repository is a bit overkill for me (beside the
> additional constraints of preventing network access during build).
Oh! I lost the start of this thread, but I interested in this question too. I 
only could make the patch set in dom0 with a entire retrival of the mercury 
repository and diff it with a vanilla source. I agree this is a unnecessary 
step, and I wanna find a better solution.

Xen-devel mailing list