| commit | 121e43fa53ca6d874aa3e5a7664c9b769f2cbfa6 | |
| author | Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com> | |
| Wed, 6 Sep 2017 06:48:09 +0000 (6 08:48 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 7 Sep 2017 00:52:18 +0000 (7 09:52 +0900) | ||
| tree | 7d58368b0500ddbfcf80d5e188c33e2eee126ebe | treesnapshot (tar.gz zip) |
| parent | cad0c6928eae87dc8619b035e4eced5f2c662a12 | commitdiff |
pull: honor submodule.recurse config option
"git pull" supports a --recurse-submodules option but does not parse the
submodule.recurse configuration item to set the default for that option.
Meanwhile "git fetch" does support submodule.recurse, producing
confusing behavior: when submodule.recurse is enabled, "git pull"
recursively fetches submodules but does not update them after fetch.
Handle submodule.recurse in "git pull" to fix this.
Reported-by: Magnus Homann <magnus@homann.se>
Signed-off-by: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
"git pull" supports a --recurse-submodules option but does not parse the
submodule.recurse configuration item to set the default for that option.
Meanwhile "git fetch" does support submodule.recurse, producing
confusing behavior: when submodule.recurse is enabled, "git pull"
recursively fetches submodules but does not update them after fetch.
Handle submodule.recurse in "git pull" to fix this.
Reported-by: Magnus Homann <magnus@homann.se>
Signed-off-by: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/pull.c | diffblobblamehistory | |
| t/t5572-pull-submodule.sh | diffblobblamehistory |