diff options
author | Philippe Blain <levraiphilippeblain@gmail.com> | 2021-07-16 03:02:57 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2021-07-20 14:57:43 -0700 |
commit | 878b3997345593d05f7c97a4e17a6c8bb9aba1a2 (patch) | |
tree | 022a60013f08334ebaf92511fb8614e9fedfe17d /fuzz-pack-headers.c | |
parent | Git 2.32 (diff) | |
download | tgif-878b3997345593d05f7c97a4e17a6c8bb9aba1a2.tar.xz |
doc: clarify description of 'submodule.recurse'
The doc for 'submodule.recurse' starts with "Specifies if commands
recurse into submodles by default". This is not exactly true of all
commands that have a '--recurse-submodules' option. For example, 'git
pull --recurse-submodules' does not run 'git pull' in each submodule,
but rather runs 'git submodule update --recursive' so that the submodule
working trees after the pull matches the commits recorded in the
superproject.
Clarify that by just saying that it enables '--recurse-submodules'.
Note that the way this setting interacts with 'fetch.recurseSubmodules'
and 'push.recurseSubmodules', which can have other values than true or
false, is already documented since 4da9e99e6e (doc: be more precise on
(fetch|push).recurseSubmodules, 2020-04-06).
Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'fuzz-pack-headers.c')
0 files changed, 0 insertions, 0 deletions