doc: mention that 'git submodule update' fetches missing commits
'git submodule update' will fetch new commits from the submodule remote if the SHA-1 recorded in the superproject is not found. This was not mentioned in the documentation. Helped-by: Junio C Hamano <gitster@pobox.com> Helped-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Philippe Blain committed
Nov 23, 2019 at 21:01 UTC
f0e58b3fe85970cfac20cd10545dd91a65094887
1 file changed
+2
-1
Documentation/git-submodule.txt
+2
-1
@@ -133,7 +133,8 @@ update [--init] [--remote] [-N|--no-fetch] [--[no-]recommend-shallow] [-f|--forc
133
+
134
--
135
Update the registered submodules to match what the superproject
136
-expects by cloning missing submodules and updating the working tree of
136
+expects by cloning missing submodules, fetching missing commits
137
+in submodules and updating the working tree of
138
the submodules. The "updating" can be done in several ways depending
139
on command line options and the value of `submodule.<name>.update`
140
configuration variable. The command line option takes precedence over