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

[bughound]

The shallow clone approach sounds ideal for this case.

The central server maintains the entire hg manifest while allowing users to
clone local repos with a much smaller hg manifest which represents the last
time window (say, the last week, month, etc).

Thus as the manifest grows it doesn't adversely affect the end user and
keeps resource utilization to a minimum.

It sounds like availability for this shallow clone feature is a ways off.

In the meantime I'll need to hack together another way of accomplishing
this.


-- 
View this message in context: http://www.nabble.com/.hg-directory-has-eclipsed-3GB---how-to-deal-with-huge-manifest--tp21449032p21458893.html
Sent from the Mercurial mailing list archive at Nabble.com.