summaryrefslogtreecommitdiff
path: root/git-pull.sh
diff options
context:
space:
mode:
authorJens Lehmann <Jens.Lehmann@web.de>2010-11-10 23:55:41 (GMT)
committerJunio C Hamano <gitster@pobox.com>2010-11-12 23:06:03 (GMT)
commitc1a3c3640deb8bd6929026a55b18feb1dda74e77 (patch)
tree8dc29f8d815f7dff07895414f4cb5bd21857bb92 /git-pull.sh
parentbe254a0ea99b441a6c514cb8b25cd72357383700 (diff)
downloadgit-c1a3c3640deb8bd6929026a55b18feb1dda74e77.zip
git-c1a3c3640deb8bd6929026a55b18feb1dda74e77.tar.gz
git-c1a3c3640deb8bd6929026a55b18feb1dda74e77.tar.bz2
Submodules: Add the "fetchRecurseSubmodules" config option
The new boolean "fetchRecurseSubmodules" config option controls the behavior for "git fetch" and "git pull". It specifies if these commands should recurse into submodules and fetch new commits there too and can be set separately for each submodule. In the .gitmodules file "submodule.<name>.fetchRecurseSubmodules" entries are read before looking for them in .git/config. Thus settings found in .git/config will override those from .gitmodules, thereby allowing the user to ignore settings given by the remote side while also letting upstream set reasonable defaults for those users who don't have special needs. This configuration can be overridden by the command line option "--[no-]recurse-submodules" of "git fetch" and "git pull". Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-pull.sh')
0 files changed, 0 insertions, 0 deletions