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

RE: [Xen-devel] motivation for sparse trees?


  • To: "Hollis Blanchard" <hollisb@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Fri, 9 Sep 2005 19:04:09 +0100
  • Delivery-date: Fri, 09 Sep 2005 18:02:06 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcW1Zapmmo5wVwocReiNxar7l7ScMwAAwJag
  • Thread-topic: [Xen-devel] motivation for sparse trees?

> 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?

The plan is to move to a sperate Linux hg tree as part of preparing code
for mergeing. 

The motivation for the sparse tree is that it massively reduces the size
of the repo, and serves to highlight the files we've modified.

Ian

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


 


Rackspace

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