Re: tip wanted: faster git clone

Thanks Kent. On my desktop depth=500 is 3x longer than 1, but still mightily tolerable. I didn't test full clone as I know it takes many minutes on this machine and network connection (edited for brevity): $ time git clone --depth=1 https://github.com/leo-editor/leo-editor d1 real0m11.494s

Re: tip wanted: faster git clone

Below demonstrates the difference between clone and clone --depth=1 When git trunk is recommended as a good way for users to install and run, I think --depth=1 would be good to mention, pretty dramatic difference. ktenney@delly:/tmp$ time git clone --depth=1

Re: tip wanted: faster git clone

Oh, I didn't realize unshallowing was added! I retract my statement. Without that feature I find that a repository without history is bad for development because of the lack of bisect. On Fri, Dec 8, 2017, 12:50 Matt Wilkie wrote: > Thanks Jacob! > > It seems that --depth=x

Re: tip wanted: faster git clone

Thanks Jacob! It seems that --depth=x a.k.a. Shallow Clones used to be a problem prior to Git v1.9 but are now more fully featured. They're still downplayed in "merge-based workflows" but not an actual problem anymore:

Re: tip wanted: faster git clone

if just want pull lasted code we can base svn got them from githu On Fri, Dec 8, 2017 at 10:34 PM, Terry Brown wrote: > On Fri, 08 Dec 2017 05:01:29 + > Jacob MacDonald wrote: > >> Check out the documentation for the `--depth` flag to `git-clone`.

Re: tip wanted: faster git clone

On Fri, 08 Dec 2017 05:01:29 + Jacob MacDonald wrote: > Check out the documentation for the `--depth` flag to `git-clone`. It > will pull only the selected number of commits from a single branch, > which means your initial clone is far smaller. However, it makes it >

Re: tip wanted: faster git clone

Check out the documentation for the `--depth` flag to `git-clone`. It will pull only the selected number of commits from a single branch, which means your initial clone is far smaller. However, it makes it very difficult to do development later, so make sure the clone will only be used for

tip wanted: faster git clone

Somebody (Kent?) posted a git clone command that was faster than the typical: git clone https://github.com/leo-editor/leo-editor.git I think it involved telling git there was no need to go back to the beginning of time, just the previous N months. Or something? matt -- You received this