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

Initial git clone behaviour

From
ECEric Curtin <ericcurtin17@gmail.com>
Date
Jan 6, 2016, 22:26 UTC
Message-ID
<CANpvso58uPtMcz_L0D=WBcCj+mSLLYZ5LpfO1i5yLo-jrb6bsA@mail.gmail.com>
Hi Guys,

I am not a git developer or a git expert but just a change I would love to see.

When I clone a really large repository (like the linux kernel for example) initially on a brand new machine, it can take quite a while before I can start working with the code.

Often I do a standard git clone:
git clone (name of repo)

Followed by a depth=1 clone in parallel, so I can get building and working with the code asap:

git clone --depth=1 (name of repo)

Could we change the default behavior of git so that we initially get all the current files quickly so that we can start working them and then getting the rest of the data? At least a user could get to work quicker this way. Any disadvantages of this approach? Maybe I am not the first to suggest something like this.

Next: Junio C Hamano
Message 1 of 3 in “Initial git clone behaviour”
  1. Eric CurtinJan 6, 2016
  2. Junio C HamanoJan 6, 2016
  3. Eric CurtinJan 6, 2016

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.