Re: 'git submodules update' ignores credential.helper config of the parent repository

From: Stefan Beller <sbeller@google.com>
Date: Feb 28, 2017, 18:05 UTC
Message-ID: <CAGZ79kb8F9_9fd9uhfPpHVPQj-zm99qt5Tr=3TUhpe=K6JknEg@mail.gmail.com>
In-Reply-To: <20170228143710.smbzo6b7wefjc62r@sigill.intra.peff.net>

On Tue, Feb 28, 2017 at 6:37 AM, Jeff King <peff@peff.net> wrote:

Show 8 quoted lines

>>
>> This would change the semantics of a config file as the attribute for
>> each setting depends on the location (was attribute.FOO.read =
>> {true, false} read before).
>
> I'm not enthused by this, just because there is a hidden dependency
> between attribute.* sections and other ones. They _look_ like regular
> config keys, but they really aren't.

True.

> I have a feeling that something like this would create unwelcome corner
> cases in the config-writer, which is otherwise does not have to care
> about which existing section of a file it adds a key to.

Yeah the writer would become a lot more involved, if we're not going the stupid way (add these sections for nearly all keys. that would be a mess but easy to implement)

So I guess then we rather settle with multiple config files or a white/blacklist of config options to propagate from the superproject to its submodules.