Re: [PATCH] Teach remote machinery about remotes.default config variable

Mark Levedahl [off-list ref] writes:

Junio C Hamano wrote:

quoted

Sorry, I may be missing something.

Even if you have a submodule, you can go there and that will be
a valid freestanding repository.  You can always be explicit,
bypassing any behaviour that defaults to 'origin' to avoid
ambiguity.

"git-submodule update" *requires* that origin is defined in all
sub-modules. There is no way to avoid this behavior.

Ahh.

Does that suggest the new configuration thing is only about the
"submodule update" command, not "remotes.default" that affects
how the non-submodule merge and fetch works?