Feature idea: partial cloning/pulling

Pierre-Yves David pierre-yves.david at logilab.fr
Wed Oct 10 04:36:56 CDT 2012

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 a
> 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 new
> 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 all
> over again.
> Alternatively, an implementation that would allow to do the following in a
> 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


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20121010/8b5b8db1/attachment.pgp>

More information about the Mercurial-devel mailing list