ShallowClone, partial history clone
Michael Augustin
maugustin at gmx.net
Sat Jul 26 08:20:00 UTC 2014
Hi,
What about the partial history clone topics described in the wiki?
Would this be a topic for the sprint in Munich?
Some links:
http://mercurial.selenic.com/wiki/TrimmingHistory
http://mercurial.selenic.com/wiki/OverlayRepository
http://mercurial.selenic.com/wiki/ShallowClone
Most of this pages are marked as "no longer relevant" - is that true? The longer I'm working on a big project the situation of cloning history, that is not relevant or even visible to most of the developers, but the full repository must always be cloned to each developers maschine.
As a workaround - until shallowclone feature is supported by hg :-) - I'm working with a subversion server, hgsubversion and mercurial/totoisehg. While only a part (about one year history) of the development trunk is cloned via hgsubversion into hg repo. Full history is always available in SVN. That way the HG repo size can be choosen without loosing history (in svn) on source code.
This setup has of course drawbacks as a single-branch-hgsubversion-clone is very limited. That's why a shallow clone support in HG would be a great feature for using HG in big and long running enterprise projects and point against subversion.
Kind regards
Michael
More information about the Mercurial
mailing list