Sometimes the history of a submodule is not considered important by
the projects upstream. To make it easier for downstream users, allow
a field 'submodule.<name>.depth' in .gitmodules, which can be used
to indicate the recommended depth.
Stefan Beller (3):
submodule update: make use of the existing fetch_in_submodule function
submodule-config: keep `depth` around
submodule update: learn `--recommended-depth` option
Documentation/git-submodule.txt | 10 ++++++++--
builtin/submodule--helper.c | 8 +++++++-
git-submodule.sh | 11 +++++++++--
submodule-config.c | 16 ++++++++++++++++
submodule-config.h | 1 +
t/t5614-clone-submodules.sh | 34 ++++++++++++++++++++++++++++++++++
6 files changed, 75 insertions(+), 5 deletions(-)
--
2.9.0.rc0.3.g892bdd0.dirty
base-commit: 3a0f269e7c82aa3a87323cb7ae04ac5f129f036b