WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] motivation for sparse trees?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] motivation for sparse trees?
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Fri, 9 Sep 2005 12:39:04 -0500
Delivery-date: Fri, 09 Sep 2005 17:38:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: IBM Linux Technology Center
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.2
Hi, sorry if I've missed the explanation somewhere, but what's the motivation 
for keeping sparse trees for the OSs instead of full trees?

For PPC work, we've been using a full hg Linux tree, and it's made things very 
convenient to pull, merge, and diff work with upstream. In fact I think every 
Linux developer out there has multiple trees, even though they probably 
aren't modifying more than a dozen for any particular project. Any reason we 
don't do this with Xen development?

-- 
Hollis Blanchard
IBM Linux Technology Center

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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