On Wed, Jan 03, 2018 at 09:47:28PM +0000, Jeff Hostetler wrote: > Config values of true and false control non-porcelain formats > for compatibility reasons as previously discussed. In the > last commit I added a new value of 2 for the config setting > to allow porcelain formats to inherit the new setting. I've > marked this experimental for now or so that we can discuss > it. I'm mildly negative on this "level 2" config. If influencing the porcelain via config creates compatibility headaches, then why would we allow it here? And if it doesn't, then why do we need to protect against it? This seems to exist in a funny middle ground that cannot decide whether it is bad or not. It's like we're inserting a foot-gun, but putting it just far enough out of reach that we can blame the user when they shoot themselves with it. Is there a compelling use case for this? From the previous discussion, this is the strawman I came up with: Scripted callers like Visual Studio don't want to unconditionally pass --no-ahead-behind, because it makes sense only for large repositories (and small ones would prefer the more exact answer, if we can get it cheaply). So we'd like the user to trigger "this is large" on a per-repo basis, and accept the consequences of possibly broken porcelain callers. I think we could have the best of both worlds, though, if the existing config option were coupled with a command-line option to say "yes, I understand no-ahead-behind, so use it for the porcelain if applicable". IOW, the user does: git config status.aheadbehind false and VS does: git status --ahead-behind=maybe and together both sides have assented to the "quick" thing. -Peff
