git clone algorithm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have already posted this message on git-users@xxxxxxxxxxxxxxxx but I have been 
advised to rather use this list. I know that there is a related thread 
(http://thread.gmane.org/gmane.comp.version-control.git/207257), but I don't 
think that this provides an answer to my question (me too I am on a slow 3G 
connection :))

I am wondering what algorithm is used by git clone command ? 
When cloning from remote repositories, if there is a link failure and
the same command is issued again, the process should be smart enough
to figure out what objects have been already transferred locally and
restart the cloning process from the point it has been interrupted.
As far as I can tell this is not the case, each time I have restarted
the cloning process everything started from the beginning. This is
extremely annoying with slow, unreliable connections. Are there any
ways to cope with this situation or any future plans ?

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]