Re: case sensitivity questions - oh no!!

Hi folks,

Firstly, sorry to have broken the thread. Thunderbird seems unable to
reply to individual messages in the digest at present.

A couple of suggestions for this perennial problem:

1. Martin, maybe you could add an optional section to your pre-commit
hook which restricts the character set allowed in filenames to ones you
*know* how to case fold, pure ASCII in the limiting case. eg. the
subversion project has committers from all over the world, but filenames
are always ASCII (and log messages in english). It is up to the hook
installer to decide what character set should be used for their repository.

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
identical, but have still generated the 'file exists' error then the
collision must be due to case-sensitivity. This method does not require
any knowledge of how the local filesystem does its case-folding.

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