doc: submodule.*.branch config is keyed by name
Ever since 941987a5 (git-submodule: give submodules proper names, 2007-06-11) introduced the ability to move a submodule from one path to another inside its superproject tree without losing its identity, we should have consistently used submodule.<name>.* to access settings related to the named submodule. Signed-off-by: W. Trevor King <wking@tremily.us> Signed-off-by: Junio C Hamano <gitster@pobox.com>
W. Trevor King committed
Mar 27, 2014 at 14:06 UTC
7c15fe92acf267f7538d8f4bece33d6bc8409cd7
1 file changed
+1
-1
Documentation/git-submodule.txt
+1
-1
@@ -162,7 +162,7 @@ update::
162
+
163
For updates that clone missing submodules, checkout-mode updates will
164
create submodules with detached HEADs; all other modes will create
165
-submodules with a local branch named after `submodule.<path>.branch`.
165
+submodules with a local branch named after `submodule.<name>.branch`.
166
+
167
For updates that do not clone missing submodules, the submodule's HEAD
168
is only touched when the remote reference does not match the