Subject: Re: [PATCH v4] clone: update submodule.recurse in config when using --recurse-submodule

From: Junio C Hamano <[email-masked]>
Date: Mon, 09 Aug 2021 14:15:05 -0700

"Mahi Kolla via GitGitGadget" <[email-masked]> writes:

> From: Mahi Kolla <[email-masked]>
>
> When running 'git clone --recurse-submodules', developers might expect various other commands such as 'pull' and 'checkout' to also run recursively into submodules. Set 'submodule.recurse' to true when 'git clone' is run with '--recurse-submodules'.

Please wrap overlong lines in your proposed log message to say 70 or
so columns.

Some developers might expect, but wouldn't some others want to see
this not set to true, but want to recurse only into some but not all
submodules?

Is it possible to avoid changing the behaviour unconditionally and
potentially breaking existing users by making it an opt-in feature,
e.g. "git clone --recurse-submodules" would work as the current
users would expect, while "git clone --recurse-submodules=sticky"
would set submodule.recurse to true, or something?