Re: [PATCH v5 1/4] implement submodule config API for lookup of .gitmodules values

Heiko Voigt [off-list ref] writes:

On Thu, Jul 09, 2015 at 01:00:10PM -0700, Junio C Hamano wrote:

quoted

Jens Lehmann [off-list ref] writes:

quoted

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"?

I think he actually meant "git config" and that is already implemented.
When I implemented the infrastructure to read configurations from blobs,
Peff extended it so it will be exposed via the config command line. E.g.
you can do:

	git config --blob HEAD^^^:.gitmodules <value>

to get .gitmodules configurations from the history, so that is already
implemented.  And for reading .gitmodules values we probably do not need
more,...

Ah, I see.  Thanks.