summaryrefslogtreecommitdiff
path: root/git-pull.sh
diff options
context:
space:
mode:
authorJens Lehmann <Jens.Lehmann@web.de>2011-03-06 22:13:36 (GMT)
committerJunio C Hamano <gitster@pobox.com>2011-03-09 21:10:35 (GMT)
commite5f522d610d34914e3fcf8b23de1b771c467196e (patch)
treefe09323e53774a471c2b899a20c586b2eb4a917f /git-pull.sh
parentc16c3e40b5908ecf28be12b1caf266c7ab8de3c6 (diff)
downloadgit-e5f522d610d34914e3fcf8b23de1b771c467196e.zip
git-e5f522d610d34914e3fcf8b23de1b771c467196e.tar.gz
git-e5f522d610d34914e3fcf8b23de1b771c467196e.tar.bz2
submodule update: Don't fetch when the submodule commit is already present
If the commit to be checked out on "git submodule update" has already been fetched in the submodule there is no need to run "git fetch" again. Since "git fetch" recently learned recursion (and the new on-demand mode to fetch commits recorded in the superproject is enabled by default) this will happen pretty often, thereby making the unconditional fetch during "git submodule update" unnecessary. If the commit is not present in the submodule (e.g. the user disabled the fetch on-demand mode) the fetch will be run as before. 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