Merge branch 'sb/clone-shallow-passthru'

Fix an unintended regression in v2.9 that breaks "clone --depth"
that recurses down to submodules by forcing the submodules to also
be cloned shallowly, which many server instances that host upstream
of the submodules are not prepared for.

* sb/clone-shallow-passthru:
clone: do not let --depth imply --shallow-submodules

diff --cc Documentation/git-clone.txt
index 1b15cd7b16620e588d21e1c69a01e2e5d880729e,c5a1ce2f59d31ab559b2ffce42ddcbc85d83d319..ec41d3d698a1bcffac3b3a21489b61cc74f9d8d0
--- 1/Documentation/git-clone.txt
--- 2/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@@ -189,11 -190,10 +189,10 @@@ objects from the source repository int
  
  --depth <depth>::
        Create a 'shallow' clone with a history truncated to the
 -      specified number of revisions. Implies `--single-branch` unless
 +      specified number of commits. Implies `--single-branch` unless
        `--no-single-branch` is given to fetch the histories near the
-       tips of all branches. This implies `--shallow-submodules`. If
-       you want to have a shallow superproject clone, but full submodules,
-       also pass `--no-shallow-submodules`.
+       tips of all branches. If you want to clone submodules shallowly,
+       also pass `--shallow-submodules`.
  
  --[no-]single-branch::
        Clone only the history leading to the tip of a single branch,

diff --cc builtin/clone.c
Simple merge

diff --cc t/t5614-clone-submodules.sh
Simple merge