On Tue, Feb 28, 2017 at 10:05:24AM -0800, Stefan Beller wrote: > > 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
