Re: Case insensitivity ad nauseum

[Fabian Cenedese]

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

The strange thing here is that cvs is inconsequent. It should report the
file from the entries as missing and recreate it (though not possible on
Windows) and further should report an unknown file in the directory.
But what it did is really updating the file, so it could make the connection
between the different cases partly. Either it's case sensitive or it's not.
And that was with a local repository, so no client/server issues.

bye  Fabi