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>
This commit is contained in:
parent
23d25e48f5
commit
7c15fe92ac
@ -162,7 +162,7 @@ update::
|
|||||||
+
|
+
|
||||||
For updates that clone missing submodules, checkout-mode updates will
|
For updates that clone missing submodules, checkout-mode updates will
|
||||||
create submodules with detached HEADs; all other modes will create
|
create submodules with detached HEADs; all other modes will create
|
||||||
submodules with a local branch named after `submodule.<path>.branch`.
|
submodules with a local branch named after `submodule.<name>.branch`.
|
||||||
+
|
+
|
||||||
For updates that do not clone missing submodules, the submodule's HEAD
|
For updates that do not clone missing submodules, the submodule's HEAD
|
||||||
is only touched when the remote reference does not match the
|
is only touched when the remote reference does not match the
|
||||||
|
Loading…
Reference in New Issue
Block a user