Re: Initial git clone behaviour

On 6 January 2016 at 23:14, Junio C Hamano wrote: > On Wed, Jan 6, 2016 at 2:26 PM, Eric Curtin wrote: >> >> 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 --de

Re: Initial git clone behaviour

On Wed, Jan 6, 2016 at 2:26 PM, Eric Curtin wrote: > > 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

Initial git clone behaviour

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 clon