summaryrefslogtreecommitdiff
path: root/t/t7401-submodule-summary.sh
diff options
context:
space:
mode:
authorLibravatar Sebastian Schuberth <sschuberth@gmail.com>2016-01-08 10:32:52 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-01-08 12:40:12 -0800
commit60253a605d230a7fd2b32e77e94bd620c1399b72 (patch)
tree0b4d2c93f1dd86f50442187b16750371e0e4cde7 /t/t7401-submodule-summary.sh
parentdocs: say "commits" in the --depth option wording for git-clone (diff)
downloadtgif-60253a605d230a7fd2b32e77e94bd620c1399b72.tar.xz
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>
Diffstat (limited to 't/t7401-submodule-summary.sh')
0 files changed, 0 insertions, 0 deletions