summaryrefslogtreecommitdiff
path: root/fmt-merge-msg.h
diff options
context:
space:
mode:
authorLibravatar Mahi Kolla <mkolla2@illinois.edu>2021-08-14 01:09:56 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-08-30 14:23:17 -0700
commit48072e3d68049a6bbb4f99f3a381e8b7f3647c52 (patch)
tree0bfd64a070366ff64e68875929335c95489e6b4d /fmt-merge-msg.h
parentGit 2.33-rc2 (diff)
downloadtgif-48072e3d68049a6bbb4f99f3a381e8b7f3647c52.tar.xz
clone: set submodule.recurse=true if submodule.stickyRecursiveClone enabled
Based on current experience, when running git clone --recurse-submodules, developers do not expect other commands such as pull or checkout to run recursively into active submodules. However, setting submodule.recurse=true at this step could make for a simpler workflow by eliminating the need for the --recurse-submodules option in subsequent commands. To collect more data on developers' preference in regards to making submodule.recurse=true a default config value in the future, deploy this feature under the opt in submodule.stickyRecursiveClone flag. Signed-off-by: Mahi Kolla <mkolla2@illinois.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'fmt-merge-msg.h')
0 files changed, 0 insertions, 0 deletions