Feature idea: partial cloning/pulling
dukeofgaming at gmail.com
Wed Oct 10 11:54:02 CDT 2012
lol, no worries
Yes, I mean resumable cloning (and pulling even), I think cloning part of
the files defeats some of the purpose of DVCS where you track integrity of
the whole project.
Is there a wiki page on this bundle2 stuff?
On Wed, Oct 10, 2012 at 4:36 AM, Pierre-Yves David <
pierre-yves.david at logilab.fr> wrote:
> On Tue, Oct 09, 2012 at 09:37:58PM -0500, dukeofgaming wrote:
> > Hi,
> > Just wanted to toss around an idea to the community: partial cloning.
> > I've been using the perfarce extension some time, and whenever you clone
> > perforce repository the initial repository gets configured but starts
> > writing to the change log, if the connection drops you can resume
> > downloading by doing a pull. This would be very useful when downloading
> > very big repositories.
> > If I am correct, when a clone is requested to a remote repo, the remote
> > repo will create a bundle and serve it, which is then unpacked into the
> > clone, so what I'm suggesting is the ability to clone in an unbundled
> > mode... which might be slower, but without the risk of having to start
> > over again.
> > Alternatively, an implementation that would allow to do the following in
> > more automatic way and without restarting the connection on each "step":
> > hg clone -r 0
> > hg pull -r 1
> > hg pull -r 2
> > hg pull -r <...>
> > hg pull -r <N>
> > Would something like this be feasible/sane for Mercurial?
> Sound like this could be taken in account in the coming bundle2 format
> (one of
> the magic bugaboo coming after changelog filtering is installed)
> Pierre-Yves David
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> -----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mercurial-devel