@@ -169,15 +169,15 @@ ACTIVE SUBMODULES
169
169
170
170
A submodule is considered active,
171
171
172
- a . if `submodule.<name>.active` is set to `true`
172
+ 1 . if `submodule.<name>.active` is set to `true`
173
173
+
174
174
or
175
175
176
- b . if the submodule's path matches the pathspec in `submodule.active`
176
+ 2 . if the submodule's path matches the pathspec in `submodule.active`
177
177
+
178
178
or
179
179
180
- c . if `submodule.<name>.url` is set.
180
+ 3 . if `submodule.<name>.url` is set.
181
181
182
182
and these are evaluated in this order.
183
183
@@ -193,11 +193,11 @@ For example:
193
193
url = https://example.org/baz
194
194
195
195
In the above config only the submodule 'bar' and 'baz' are active,
196
- 'bar' due to (a ) and 'baz' due to (c ). 'foo' is inactive because
197
- (a ) takes precedence over (c )
196
+ 'bar' due to (1 ) and 'baz' due to (3 ). 'foo' is inactive because
197
+ (1 ) takes precedence over (3 )
198
198
199
- Note that (c ) is a historical artefact and will be ignored if the
200
- (a ) and (b ) specify that the submodule is not active. In other words,
199
+ Note that (3 ) is a historical artefact and will be ignored if the
200
+ (1 ) and (2 ) specify that the submodule is not active. In other words,
201
201
if we have a `submodule.<name>.active` set to `false` or if the
202
202
submodule's path is excluded in the pathspec in `submodule.active`, the
203
203
url doesn't matter whether it is present or not. This is illustrated in
0 commit comments