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] Can the qemu-xen git repository be moved to a 'git://' p

To: stefano.stabellini@xxxxxxxxxxxxx, tom.rotenberg@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Can the qemu-xen git repository be moved to a 'git://' protocol? It can save a lot of time...
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 04 Aug 2009 16:59:45 -0700
Delivery-date: Tue, 04 Aug 2009 17:00:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090717171113.GA81140@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <8686c3cd0907160136n5ce18d54ncb2dbeecd3bcae1c@xxxxxxxxxxxxxx> <20090716230314.GC64261@xxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0907171109190.24787@kaball-desktop> <20090717171113.GA81140@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2
On 07/17/09 10:11, Brendan Cully wrote:
> Ah, wonderful. Would it make sense to use this tree by default? We can
> assume users already have hg working to pull the master tree, and it
> means one less confusing build tool. The git tree doesn't seem to me
> to offer any advantages over an hg mirror for the majority of users,
> but it does increase the number of complicated moving parts in an
> already difficult build system.

+1.  Presumably using something like the forest extension would help here.


Xen-devel mailing list

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