Jens Lehmann <jens.lehm...@web.de> writes: >> How does git-submodule access this information? It looks like it just >> hits "git config -f .gitmodules" directly. Perhaps whatever interface is >> designed should be suitable for its use here (and if there really is no >> more interesting interface needed, then why is "git config" not good >> enough for other callers?). > > The git-submodule script doesn't need this and is fine using plain old > "git config", as by the time it is run the .gitmodules file is already > updated in the work tree. Heiko's series is about adding infrastructure > to allow builtins like checkout and friends to access the configuration > values from the .gitmodules file of the to-be-checked-out commit when > run with "--recurse-submodules". And yes, if we want to expose this > functionality to users or scripts some day "git config" looks like the > best place to do that to me too.
Did you mean "git submodule config"? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
