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

Re: git fails on large repo clone on intermittent, or intermittently-high-latency, connections

From
James Cloos <cloos@jhcloos.com>
Date
Jan 9, 2011, 20:04 UTC
Message-ID
<m38vyt7shs.fsf@jhcloos.com>
In-Reply-To
<AANLkTinkhmHpAQjraviKjqFAczThR5GtT_qdyf6Sb3nm@mail.gmail.com>

In addition to the other replies, if you have a shell login elswhere you can clone there, bundle the file, and use rsync, http, ftp or the like to copy it down.

If the remote site's git is too old to have git bundle, use a bare clone and tar it. You will not need to compress the tar.

You can also use split(1) to break up the bundle or tar into smaller chunks if that helps. cat(1) will happily recombine those chunks.

If git bundle was not available, you can use the copied bare repo as a --reference for a new clone, then copy the bare's pack file into that new clone and remove the new clone's objects/info/alternates file.

I've had to use that method to get a clean clone across a small straw (dialup or wireless) for several large repositories over the years.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6
Previous: Jakub Narebski
Message 5 of 5 in “git fails on large repo clone on intermittent, or intermittently-high-latency, connections”
  1. Zenaan HarknessJan 5, 2011
  2. Jakub NarebskiJan 5, 2011
  3. Jonathan NiederJan 5, 2011
  4. Jakub NarebskiJan 5, 2011
  5. James CloosJan 9, 2011

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.