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

Re: Yet another Case-Insensitive File System Problem

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2003-07-30 19:21:57 CEST

John Peacock wrote:

> What bugs me the most is that this is not a very nice way for the svn
> client to act. It means that the repository is virtually inaccessible,
> but only from a specific O/S; everywhere else it is fine. If I could
> check out the repos, with warnings, rather than having it error out,
> that would be acceptable I think.

The problem is, this is rather core to the Subversion philosophy with
regard to files and directories. We version tree structures, and you
are talking about two different parts of the tree. Automatically
merging them just because they have similar names is not a trivial thing
to do, and I'm not convinced it's the right thing to do. There are
entirely too many platform dependent restrictions on the names of files
and directories, we can't hope to catch them all, and even if we detect
it, it still seems like the 'right thing to do' is just to give a nicer
error message explaining the problem. This is what you get when you
version directories, it's not a bug, IMO, it's a fundamental feature of
how the system works.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 30 19:22:52 2003

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.