Eric Wilhelm wrote:
># The following was supposedly scribed by
># Stan Devyatovsky
># on Monday 21 June 2004 08:18 am:
>
>
>>So I suggest not to force users to work around this problem, but
>>automate this workaround in Subversion, just so that the users
>>wouldn't have to worry about it at all.
>>
>>
>I don't think it's subversion's cross to bear. I'd rather see the users of
>such flawed file systems realize those flaws.
>
>
A case-insensitive file system isn't "flawed", it just behaves slightly
differently than a case-sensitive file system. You'd be quite as correct
to say that a filesystem that allows newlines in file names is flawed.
>>What needs to be done in Subversion to solve this issue? Just a couple
>>of things:
>>1. Force "svn rename Index.html index.html" to internally execute just
>>as if we were executing:
>>"svn rename svn://server/repos/Index.html svn://server/repos/index.html"
>>
>>
>This is not a good default behavior.
>
It is, in fact (except fot the implicit commit that's part of the
URL->URL rename, of course).
>IMO subversion should not go out of its
>way to make provisions for the failures of a file system. But if it does
>anything to help solve this problem (read: "somebody else's problem), it
>shouldn't be a default behavior.
>
>
I disagree. It's long been our principle for Subversion to behave as
much like a native application as possible, on all platforms. This
includes supporting case-only renames on, for example, Mac OS X. We've
not always acheived this goal, but we're definitely getting there.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 21 15:41:41 2004