[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Diederik van Arkel <vanarkel_at_knoware.nl>
Date: 2005-07-26 17:25:13 CEST

On Jul 26, 2005, at 3:20 PM, 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?
> 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.

One that I have occasionally run into:

[Macintosh:~/WC] diederik% svn ci -m 'update parser scanner grammars'
CleanParse/CleanScanner.x cleanParse/CleanParser.y
svn: Working copy '/Users/diederik/WC/cleanParse' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for

Here the case of the directories doesn't match leading to an error with
directory locking.
I'm not sure if this exists in 1.2.x or trunk as I'm still using 1.1.x


Diederik van Arkel

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 26 17:25:54 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.