projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 282616c) | patch
docs: clarify that passing --depth to git-clone implies --single-branch
authorSebastian Schuberth <sschuberth@gmail.com>
Wed, 6 Jan 2016 13:06:47 +0000 (14:06 +0100)
committerJunio C Hamano <gitster@pobox.com>
Thu, 7 Jan 2016 19:45:19 +0000 (11:45 -0800)
commit28a1b56932c222b326e4ac0cd480d4e0be72fb1c
tree0b530bc26f1da30146ba3efd11f0606e779e7a5dtree | snapshot
parent282616c72d1d08a77ca4fe1186cb708c38408d87commit | diff
docs: clarify that passing --depth to git-clone implies --single-branch

It is confusing to document how --depth behaves as part of the
--single-branch docs. Better move that part to the --depth docs, saying
that it implies --single-branch by default.

Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-clone.txt diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.