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

A local shared clone is now much slower

From
SRStephen Rothwell <sfr@canb.auug.org.au>
Date
Jul 8, 2013, 03:03 UTC
Message-ID
<20130708130355.647fffb6e5b6a453bfa0fa6e@canb.auug.org.au>
Hi guys,

So commit 0433ad128c59 ("clone: run check_everything_connected") (which turned up with v1.8.3) added a large traversal to clone which (as the comment said) makes a clone much slower. It is especially noticeable on "git clone -s -l -n" which I use every day and used to be almost instant. Is there any thought to making it fast again, please?

The above clone is very useful for working with different branches in one tree without touching every file in the main branch you are working with (and consequent issues with rebuilding at least). As linux-next maintainer, you can imagine that I do this a bit.

I am sure one of Linus' points about branches was that being able to make a fast local clone of a tree to use more than one branch was a feature.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
Next: Duy Nguyen
Message 1 of 10 in “A local shared clone is now much slower”
  1. Stephen RothwellJul 8, 2013
  2. Duy NguyenJul 8, 2013
  3. Stephen RothwellJul 8, 2013
  4. Jeff KingJul 8, 2013
  5. Duy NguyenJul 8, 2013
  6. Junio C HamanoJul 8, 2013
  7. Jeff KingJul 9, 2013
  8. Priming git clone with a local repo?Andreas Krey, Jul 11, 2013
  9. Junio C HamanoJul 11, 2013
  10. Junio C HamanoJul 8, 2013

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.