Re: git cvsimport and case-insensitive config
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 30, 2010, 21:20 UTC
- Message-ID
- <7vr5n1v74x.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <cb7bb73a1003301105v691624sdcdadf6809c50b89@mail.gmail.com>
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).
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.