Lazy remote clones?
Martin Geisler
mg at daimi.au.dk
Thu Mar 27 02:47:20 CDT 2008
"Andreas Axelsson" <andreas.axelsson at gmail.com> writes:
> So, I was thinking that perhaps it would be possible to replace
> historical content with pointers to a "master" repository. Most of
> the time you don't need to diff against or view old versions of
> binaries, but you do need the history intact, and it's not uncommon
> that you need to recreate old builds or patch previous releases. So,
> I would propose two features:
I can see how this would be very interesting for big projects with
many binary files. The Wiki has two pages on this subject:
http://www.selenic.com/mercurial/wiki/index.cgi/TrimmingHistory
http://www.selenic.com/mercurial/wiki/index.cgi/OverlayRepository
--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
More information about the Mercurial
mailing list