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

From: Jeff King <peff@peff.net>
Date: Feb 28, 2017, 20:08 UTC
Message-ID: <20170228200821.iojdzntjslwgrzcb@sigill.intra.peff.net>
In-Reply-To: <CAGZ79kb8F9_9fd9uhfPpHVPQj-zm99qt5Tr=3TUhpe=K6JknEg@mail.gmail.com>

On Tue, Feb 28, 2017 at 10:05:24AM -0800, Stefan Beller wrote:

Show 10 quoted lines

> > 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.

I'm still open to the idea that we simply improve the documentation to make it clear that per-repo config really is per-repo, and is not shared between super-projects and submodules. And then something like Duy's proposed conditional config lets you set global config that flexibly covers a set of repos.

-Peff