(This is a resend of a series from March 15th, titled "Towards sane shallow clones with submodules", this series applies on top of sb/submodule-parallel-update, it replaces sb/clone-shallow-passthru) When creating a shallow clone of a repository with submodules, the depth argument does not influence the submodules, i.e. the submodules are done as non-shallow clones. It is unclear what the best default is for the depth of submodules of a shallow clone, so we need to have the possibility to do all kinds of combinations: * shallow super project with shallow submodules e.g. build bots starting always from scratch. They want to transmit the least amount of network data as well as using the least amount of space on their hard drive. * shallow super project with unshallow submodules e.g. The superproject is just there to track a collection of repositories and it is not important to have the relationship between the repositories intact. However the history of the individual submodules matter. * unshallow super project with shallow submodules e.g. The superproject is the actual project and the submodule is a library which is rarely touched. The new switch to select submodules to be shallow or unshallow supports all of these three cases. Changes to the previous series: * Reordered patch 1 and 2, as it sounds like a more natural ordering. Any comments welcome! Thanks, Stefan Stefan Beller (3): clone: add `--shallow-submodules` flag submodule clone: pass along `local` option clone: Add t5614 to test cloning submodules with shallowness involved Documentation/git-clone.txt | 13 +++++-- builtin/clone.c | 21 ++++++++++++ builtin/submodule--helper.c | 22 ++++++++++-- git-submodule.sh | 7 ++++ t/t5614-clone-submodules.sh | 82 +++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 139 insertions(+), 6 deletions(-) create mode 100755 t/t5614-clone-submodules.sh -- 2.5.0.264.gc776916.dirty -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html