Hi Mahi,
Le 2021-08-02 à 19:23, Mahi Kolla via GitGitGadget a écrit :
When running 'git clone --recurse-submodules', developers expect various
other commands such as 'pull' and 'checkout' to also run recursively into
submodules.The submitted code updates the 'submodule.recurse' config value
to true when 'git clone' is run with the '--recurse-submodules' option.
Signed-off-by: Mahi Kolla mahikolla@xxxxxxxxxx
Mahi Kolla (4):
clone: update submodule.recurse in config when using
--recurse-submodule
clone: update submodule.recurse in config when using
--recurse-submodule
clone test: update whitespace according to style guide
clone: update whitespace according to style guide
This could all be done in a single patch. As long as the patches are not merged
to the 'next' branch, you can simply force-push and re '/submit' on Gitgitgadget.
builtin/clone.c | 1 +
t/t5606-clone-options.sh | 7 +++++++
2 files changed, 8 insertions(+)
I think this change would require a mention in the 'git-clone(1)' man page.
I'm very much in favor of a change like this. It is a pretty big change in
behaviour, but I really believe this is a good way forward. Thanks for getting
the ball rolling on this!
