Re: [RFD/PATCH] submodule doc: describe where we can configure them

From: Junio C Hamano <gitster@pobox.com>
Date: May 9, 2016, 16:19 UTC
Message-ID: <xmqqlh3jxkyn.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20160508220127.GB59077@book.hvoigt.net>

Heiko Voigt <hvoigt@hvoigt.net> writes:

Show 13 quoted lines

>> > - When upstream adds a new submodule, I have to do the same manual
>> >   work to change the options for that new submodule.
>> 
>> Because a new module is not automatically "init"ed by default?
>> 
>> Isn't "config only" vs "config with gitmodules fallback" orthogonal
>> to that issue?
>
> What do you mean with "orthogonal to that issue"? AFAICS a gitmodule
> fallback does not have that issue.
>
> Actually I would see it more like:
> .gitmodule is the default and .git/config a possibility to override.

The way I read Jonathan's "I have to do the same manual..." above is:

  Back when I cloned, the upstream had one submodule A.  I didn't like
  some aspect of the configuration for that submodule so I did a
  customization in [submodule "A"] section of .git/config for it.

  Now the upstream added another submodule B.  I want a tweak similar
  to what I did to A applied to this one, but that would mean I need
  to edit the entry in .git/config copied by "init" from .gitmodules.

I do not see how difference between ".git/config is the only source of truth" or ".git/config overrides what is in .gitmodules" would matter to the above scenario.