Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 27, 2017, 17:41 UTC
Message-ID: <xmqq1sjgoyph.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20171224143318.GC23648@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 9 quoted lines

> I, too, had a funny feeling about calling this "core". But I didn't have
> a better name, as I'm not sure what other place we have for config
> options that cross many command boundaries. "diff" and "status" don't
> seem quite right to me. While you can argue they are subsystems, it
> seems too easy for users to confuse them with the commands of the same
> names.
>
> Maybe there should be a "ui.*" config hierarchy for these kinds of
> cross-command interface options?

I had an impression that ui.* was primarily pretty-printing, colouring and things of such nature. I do not think it is such a bad idea to honor a status.frotz variable that affects how (e.g. to what degree of detailedness) status on frotz are reported in Git subcommands other than 'git status' if they report the same sort of information on 'frotz' that 'git status' makes.