Re: Git's inconsistent command line options

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 1, 2015, 16:42 UTC
Message-ID: <xmqq37yyt7k8.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20150901101924.6c350012@anarchist.wooz.org>

(Administrivia) please do not cull CC list when replying.

Barry Warsaw <barry@python.org> writes:

Show 11 quoted lines

> On Sep 01, 2015, at 02:28 AM, David Aguilar wrote:
>
>>While a script writer could write, "git -c core.cliversion=1 ...",
>>no one does that, no one wants to do that, and it just seems
>>like a bad idea that's best left unexplored.
>
> Sure, no one will do that from the command line, but I don't think people
> generally change their preferences that often.  Much more likely is that
> they'll `git config` a more permanent choice for their shell usage and then
> just use straight up "git" with the new ui.  -c would be reserved for scripts
> which hard code a particular ui.

That way, you are forcing all the existing scripts to be updated to say "git -c ..." for _all_ invocations of Git they have, aren't you?

That is simply unworkable.

By the way, you can review what has already been said in this discussion here:

  http://thread.gmane.org/gmane.comp.version-control.git/276509/focus=276589