Re: [PATCH v3 08/21] Documentation/git-update-index: talk about core.splitIndex config var

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 7, 2017, 21:38 UTC
Message-ID: <xmqqshou35zr.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAP8UFD06mxGiZmr4Lwv3M8CedBZaamswzz-Q+mOxuuUFet8KNQ@mail.gmail.com>

Christian Couder <christian.couder@gmail.com> writes:

> It feels strange that when I do things one way, you suggest another
> way, and the next time in a similar situation when I do things the way
> you suggested previously, then you suggest the way I did it initially
> the first time...

Perhaps because neither is quite satisfactory and I am being forced to choose between the two unsatifactory designs? In any case, I mostly am and was pointing out the issues and not saying the other one is the most preferred solution in these threads.

I think there should just be one authoritative source of the truth, and I have always thought it should be the bit set in the index file when the command line option is used, because that was the way the feature was introduced first and I am superstitious about end-user inertia. And from that point of view, no matter how you make this new "config" thing interact with it, it would always give a strange and unsatifactory end-user experience, at least to me.

Perhaps we should declare that config will be the one and only way in the future and start deprecating the command line option way. That will remove the need for two to interact with each other.

I dunno.