@@ -150,9 +150,8 @@ pattern in the config file. For example, if you have this in your config file:
150150 username = foo
151151--------------------------------------
152152
153- then we will match: both protocols are the same, both hosts are the same, and
154- the "pattern" URL does not care about the path component at all. However, this
155- context would not match:
153+ then we will match: both protocols are the same and both hosts are the same.
154+ However, this context would not match:
156155
157156--------------------------------------
158157[credential "https://kernel.org"]
@@ -166,11 +165,11 @@ match: Git compares the protocols exactly. However, you may use wildcards in
166165the domain name and other pattern matching techniques as with the `http.<URL>.*`
167166options.
168167
169- If the "pattern" URL does include a path component, then this too must match
170- exactly : the context `https://example.com/bar/baz.git ` will match a config
171- entry for `https://example.com/bar/baz.git` (in addition to matching the config
172- entry for `https://example.com`) but will not match a config entry for
173- `https://example.com/bar` .
168+ If the "pattern" URL does include a path component, then this must match
169+ as a prefix path : the context `https://example.com/bar` will match a config
170+ entry for `https://example.com/bar/baz.git` but will not match a config entry for
171+ `https://example.com/other/repo.git` or `https://example.com/barry/repo.git`
172+ (even though it is a string prefix) .
174173
175174
176175CONFIGURATION OPTIONS
0 commit comments