Re: CaSe insensetive OS not handled well

>> On OS-es that does not distinguish between file.c and File.C working
>> with subversion leads from annoying results to a loss of data.

> Loss of data? how?

In the TSVN mailing lists there were a couple of examples - commits
were commiting as a new file and then upon checking out... I don't
remember how but those who were affected have remembered this for sure
:)

>> not just about the urls, the filenames, but a side things like ignore
>> files - xx.tmp, xx.Tmp, XX.TMP, etc are the same file under windows

> You can use expressions like *.[tT][mM][pP] I think.

Yeah... I can do that... in the ignore list which is over 50
extensions...

>> A solution:
>> #ifdef WIN32
>> #define strcmp strcmpcaseinsensitive or whatever
>> #endif
>>
>> It is an ugly solution but you got the idea.

> It's not a solution at all, because that would mean windows clients can
> no longer communicate with unix servers and vice versa.

> But I agree that it is a problem that should be handled in the long run.

Agreed. Second easy solution - an universal "comparing" function which
returns either case sensitive or insensitive compare (just uses one or
another function) based on the flag.
"What flag?" - just some flag that has to be put on the command line in
case of client wants case insensitive compare, i.e.
svn -C ....

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 19 15:18:32 2005