From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Rousse Subject: Re: building xen without mercury repository access Date: Tue, 12 Feb 2008 11:43:42 +0100 Message-ID: <47B1785E.6060504@inria.fr> References: <47B0CCFB.30709@inria.fr> <18353.29868.445494.691248@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <18353.29868.445494.691248@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ian Jackson a écrit : > Keir Fraser writes ("Re: [Xen-devel] building xen without mercury repository access"): >> On 11/2/08 22:32, "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). >> We should probably stick a tarball of our Linux tree on www.xen.org. > > Yes. But which version of our hg tree ? There aren't any release > tags and a nightly tarball from tip would look scary even if it's > actually quite stable. I don't really care, as long as it is properly identified. Keir suggested revision 406, it's OK for me (I don't track internal changes, I'm not a kernel hacker). Of course, if you could have releases, it would be better :) -- Guillaume Rousse Moyens Informatiques - INRIA Futurs Tel: 01 69 35 69 62