diff options
author | Junio C Hamano <gitster@pobox.com> | 2016-06-19 13:51:56 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2016-06-20 11:35:28 -0700 |
commit | 18a74a092bff41f1ffe10bd2463d3eed9a04435d (patch) | |
tree | 508b2f5bbad1fdf44e41f23c48dc5e14f2983d38 /t/t2003-checkout-cache-mkdir.sh | |
parent | clone: add `--shallow-submodules` flag (diff) | |
download | tgif-18a74a092bff41f1ffe10bd2463d3eed9a04435d.tar.xz |
clone: do not let --depth imply --shallow-submodules
In v2.9.0, we prematurely flipped the default to force cloning
submodules shallowly, when the superproject is getting cloned
shallowly. This is likely to fail when the upstream repositories
submodules are cloned from a repository that is not prepared to
serve histories that ends at a commit that is not at the tip of a
branch, and we know the world is not yet ready.
Use a safer default to clone the submodules fully, unless the user
tells us that she knows that the upstream repository of the
submodules are willing to cooperate with "--shallow-submodules"
option.
Noticed-by: Vadim Eisenberg <VADIME@il.ibm.com>
Helped-by: Jeff King <peff@peff.net>
Helped-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t2003-checkout-cache-mkdir.sh')
0 files changed, 0 insertions, 0 deletions