git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git clone algorithm

From
BCBogdan Cristea <cristeab@gmail.com>
Date
Oct 9, 2012, 17:23 UTC
Message-ID
<loom.20121009T192043-666@post.gmane.org>

I have already posted this message on git-users@googlegroups.com 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 ?

Next: Sitaram Chamarty
Message 1 of 2 in “git clone algorithm”
  1. Bogdan CristeaOct 9, 2012
  2. Sitaram ChamartyOct 10, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.