Re: git cvsimport and case-insensitive config

[Junio C Hamano <gitster@pobox.com>]

Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:

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

The value given to -S can just be 'tests', or even "\.", as the regexp
match is not anchored on either side:

		if ($opt_S && $fn =~ m/$opt_S/) {
		    print "SKIPPING $fn v $rev\n";
		    ...

And "-s" would likely be one or more (but not too many) non-alphanumeric
characters.

But a bigger question is if you can bet on that heuristics, and when the
heuristics does not work, what you would do.

>> 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?

What configuration?