| commit | 60253a605d230a7fd2b32e77e94bd620c1399b72 | |
| author | Sebastian Schuberth <sschuberth@gmail.com> | |
| Fri, 8 Jan 2016 09:32:52 +0000 (8 10:32 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 8 Jan 2016 20:40:12 +0000 (8 12:40 -0800) | ||
| tree | 0b4d2c93f1dd86f50442187b16750371e0e4cde7 | treesnapshot (tar.gz zip) |
| parent | fc142811d14d3acb64d1c2057a774fa1573e60cb | commitdiff |
docs: clarify that --depth for git-fetch works with newly initialized repos
The original wording sounded as if --depth could only be used to deepen or
shorten the history of existing repos. However, that is not the case. In a
workflow like
$ git init
$ git remote add origin https://github.com/git/git.git
$ git fetch --depth=1
The newly initialized repo is properly created as a shallow repo.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The original wording sounded as if --depth could only be used to deepen or
shorten the history of existing repos. However, that is not the case. In a
workflow like
$ git init
$ git remote add origin https://github.com/git/git.git
$ git fetch --depth=1
The newly initialized repo is properly created as a shallow repo.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/fetch-options.txt | diffblobblamehistory |