On Tue, Apr 04, 2017 at 10:23:52AM +0200, Ævar Arnfjörð Bjarmason wrote: > The part that confused my & I found unintuitive is that there's a new > core.WHATEVER config that'll get silently overridden by a specific > command, git-fsck. > > Nothing else I can think of in core.* works like this, i.e. it's a > namespace for "applies to all of git", core.editor, core.ignoreCase > etc. > > Having git-fsck have a command-line option that's on by default as I > suggested is one way to get out of that confusion. It makes it a > special case of a CLI option overriding some config. Yeah, I do agree your suggestion makes it slightly less confusing. I mostly just think we can avoid the situation altogether, which IMHO is preferable. -Peff