Re: Case-insensitive file names: better error messages [was: case sensitivityquestions - oh no!!]

Julian Foad wrote:
> Simon Large wrote:
>
>> 2. When a case collision does occur on the client, the error messages
>> simply says something like "a file of this name already exists" which,
>> while it is true, does not communicate the root cause very well. Is it
>> possible to define a separate error condition for case collisions? It
>> can be detected fairly easily on case-insensitive/case-preserving
>> filesystems:
>>
>> If a 'file exists' error occurs, query the filesystem for the name of
>> that file and compare with the filename SVN is using. If they are not
>
>
> I think that would be a good enhancement. Would you like to have a go
> at it?

Sorry to be so long getting back. Unfortunately I am snowed under with
work at the moment. Can this go in the issue tracker to ensure it
doesn't get forgotten.

> That collision is one way in which a case mismatch can cause a problem.
> I feel there must be other failure modes, such as a file name specified
> with the wrong case not being found internally (e.g. in the "entries"
> file) because a case-sensitive search is used. You might want to look
> for such things as well as the error that you mentioned.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org