From: Junio C Hamano <gitster@pobox.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: git cvsimport and case-insensitive config
Date: Tue, 30 Mar 2010 16:14:49 -0700 [thread overview]
Message-ID: <7vd3yls8pi.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <cb7bb73a1003301517r29aed329j4a5f38fbc9b515ca@mail.gmail.com> (Giuseppe Bilotta's message of "Wed\, 31 Mar 2010 00\:17\:31 +0200")
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?
next prev parent reply other threads:[~2010-03-30 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 8:32 git cvsimport and case-insensitive config Giuseppe Bilotta
2010-03-30 17:29 ` Junio C Hamano
2010-03-30 18:05 ` Giuseppe Bilotta
2010-03-30 21:20 ` Junio C Hamano
2010-03-30 22:17 ` Giuseppe Bilotta
2010-03-30 23:14 ` Junio C Hamano [this message]
2010-03-31 6:54 ` Giuseppe Bilotta
2010-03-31 9:45 ` Junio C Hamano
2010-03-31 11:17 ` Giuseppe Bilotta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vd3yls8pi.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.