On Wed, 22 Dec 2004 10:10:04 +0100, Niels Skou Olsen wrote:
>One reason that nobody found it *really* important yet, is that it is no
>big deal working around it! Case sensitivity is only a problem if you have
>a team using both UNIX and Windows clients on the same repository. If you
>have a pure Windows client team, nobody will be able to commit
>{test,Test,TEST} files in the same directory. If you have a pure UNIX
>client team, well no problem..
>
>So a mixed client team can setup a project policy to forbid committing
>{test,Test,TEST} files, and thus avoid the problem. Should it ever happen
>in spite of the policy, the sinner must fix the problem and bye everyone a
>beer. Then life can continue. No big deal IMHO, especially considering how
>extremely rare {test,Test,TEST} is in practice.
Actually... in my case I commited a filename with one case,
then decided I needed to change it because Tomcat is case-sensitive
(don't you get me started on that garbage...) and so I ran into this
problem. The problem is mixing of unix and win32 tools and you don't
have to have a mixed team (unix and win32) to run into this problem. It
is enough to use poorly ported tools from unix.
Gili
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 22 18:42:37 2004