> Wadsworth, Eric (Contractor) wrote:
>
>> I'm probably not the only person who has had to deal with this, and I
>> probably won't be the last. Are there plans for a better solution to this
>> problem in future versions of svn? "Better" being defined as "Easier
>> for the
>> end user" in this case. It's unlikely that the correct solution is viable
>> (fixing the non-case-sensitive OS and filesystem).
>
>
> The "correct" solution is for the user to check in the file with the
> proper case in the first place, and not try and work around it in svn
> (which works just fine on case-sensitive O/S's). This is a carbon-based
> error, nothing more...
This would be the same disadvantage as in CVS where
you have to set meta information like file attributes
correctly from beginning. SVN does it better.
And it would be cool if SVN would do it also better
in this case, too ;-)
I think the argument "but it works on another OS" is
not very helpful ;-)
I remeber painful problems with this problem in CVS;
it is very likely that we will have the same
problem with SVN some day, too...
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 18 16:31:51 2003