Sparse working copy
Jan Vrany
jan.vrany at fit.cvut.cz
Sat Nov 17 10:38:22 UTC 2012
Hi there,
>
> As far as I know, and I'm sure corrections will follow, if you have
> chosen to manage data1 and data2 in the repository then you would need
> to have their history stored within the .hg directory structure, but you
> could avoid having them "checked out" (in addition to occupying space in
> the history) by doing something like this:
>
> cd p1
> hg update null
> hg revert -r tip c1.st c2.st makefile
>
> At this point, you have three files as working, usable files but not the
> data files. I imagine that you have to be somewhat careful performing a
> revert on directories because this will make their contents available as
> working files as well.
That's interesting idea, thanks! I'll explore. Intermediate
directories might need some trickery, but...We'll see.
Remember that this only saves the additional
> space that would otherwise be occupied by those files when performing a
> normal update to a particular revision, and the .hg directory would
> still be as large as ever.
Yes, but as long as files are hardlinked, I'm fine with that.
Cheers, Jan
More information about the Mercurial
mailing list