Stefan Beller <[email protected]> writes: >> Does it mean "never appears in .git/config, and when it appears it >> will not be used at all"? If so we shouldn't even list it here. > > I meant: > Git wont put it into .git/config on its own. If you really wanted to have > it there, you need to do it yourself. > > I assumed you can overwrite the path via the config. It turns out, > the value from the config is ignored, so it doesn't even make sense > to put it into the config. Only the value from the .gitmodules file counts. > > So with that knowledge, I'll just remove it here, but I'll cross check if it > is referenced else where enough.
Good. I do recall we designed this part of the system in such a way that .path is conceptually uncostimizable (it _is_ part of what the containing tree already records), and was wondering why it is there as if it can be overridden.
