Re: Case insensitivity ad nauseum

[Jim]

>
> We once had the minor problem that somehow files showed up twice
> (e.g. doing an update). It turned out that the case of the file itself
didn't
> match the entry in the entries file. So cvs once reported the file from
> the entries file and then again while looking for unknown files. It
behaved
> correctly, it just did the file twice. But that's something the local
client
> needs to handle (I guess) and not the server. So I don't know if this has
> something to do with your actual work, I just thought I'd mention it.

Yes - if you use a poor editor it will not preserve the case of the
filenames.  FAT32, NTFS both preserve the case, even if it doesn't actually
USE the case...  It is entirely feasible to leave CVS case sensitive and
make a note somewhere that the responsibility of preserving the case is on
the user.

Jim

OOP is a frame of mind, not a language.
The difference between a bug and a feature?  A feature's documented. "What?
if I press the enter key the program crashes and makes the computer reboot?"
... "Yeah... it says right here - feature - quick reboot...."
Everything changes, what you hear today is gone tomorrow, and yesterday
might as well never have been.