.hg directory has eclipsed 3GB - how to deal with huge manifest?

[bughound]

Hans Meine-4 wrote:
> 
> On Wednesday 14 January 2009 04:29:32 bughound wrote:
>> As our project has progressed, so has the manifest (.hg directory).
>>
>> It's now over 3GB and causing anyone who wants to clone a new area a
>> 20-minute wait while the .hg directory gets populated over our network.
>>
>> What's the recommended way for resetting this?
> 
> I would use the well-known means for EditingHistory in order to remove big 
> files from the repo and use one of the means discussed recently for
> storing 
> them elsewhere.  I cannot believe your .hg got that large from source
> files, 
> did it?
> 
> /me recalls this nice idea w.r.t. special compressed file support in hg... 
> (i.e. efficient versioning of .zip/.jar file checkins) that would really
> be a 
> killer feature.  OTOH it would be hard to guarantee bitwise identical .zip 
> files in a checkout I guess (i.e. same md5sum), only the content would be 
> guaranteed to be the same.  Anyhow, this would be an extension so people
> would 
> explicitly specify that this is what they want.
> 
> Best,
>   Hans
> 
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
> 
> 

Is there an easy way to quickly identify the huge files in the manifest?
-- 
View this message in context: http://www.nabble.com/.hg-directory-has-eclipsed-3GB---how-to-deal-with-huge-manifest--tp21449032p21452737.html
Sent from the Mercurial mailing list archive at Nabble.com.