Re: git cvsimport and case-insensitive config

From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date: Mar 30, 2010, 22:17 UTC
Message-ID: <cb7bb73a1003301517r29aed329j4a5f38fbc9b515ca@mail.gmail.com>
In-Reply-To: <7vr5n1v74x.fsf@alter.siamese.dyndns.org>

On Tue, Mar 30, 2010 at 11:20 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:
>
>> We might be able to skip (2) by relying on the fact that if the
>> lowercase is boolean, the uppercase isn't, and conversely.
>
> That was the idea I wrote in an earlier draft of my response that I later
> scrapped.  I started with "cvsimport.a?  If it is 'true' then that is -a;
> if it names an existing file, then it is -A."  I continued the draft up to
> '-p' vs '-P' (the former would begin with a hyphen, the latter likely
> wouldn't).  But I don't think you can reliably guess -s/-S (both strings).

(-s likely has a single character, -S more than one. -S is likely to have * or ?, -s not.)

> A bigger reason is that, if you have _any_ combination that you cannot
> reliably guess, you would either need the user to ask for help, or you
> need to convert by reading the configuration file case-sensitively
> yourself to come up with a reliable conversion.  I opted for the latter.

Would such a configuration work at all?

-- 
Giuseppe "Oblomov" Bilotta