Ahhhhh. The monthly case-sensitivity discussion. I thought we might miss
it for the holidays.
The bigger problem is that of architecture. If someone created a
situation where StdAfx.h and stdafx.h existed in the same directory at
the same time in a Windows shop, my architect would go put a hurt on
him. The issue is more about coding standards and holding people to them
than it is about any particular tool. How did that person not know that
StdAfx.h already existed before they made stdafx.h? I guess it could
happen through a merge, but if your second developer is that
disconnected from the code, I'd be worried.
The case sensitivity issue is a platform problem, not a tool problem.
VisualStudio does it, Subversion does it, Perforce does it. ClearCase
does it. Everything does it, and every tool out there can't 'fix' the
problem in some random way when it's not really its fault/problem. UNIX
and it's ilk have capabilities that Windows does not, and if people are
working in a mixed environment, they should know that. If this is really
a problem, then maybe the wrong server architecture was chosen for the
Subversion server.
To fix it:
. move the subversion server to a windows box (not ideal or as
efficient) or
. hire an architect to develop and enforce coding standards and/or
. move, rename or merge the conflicting files together
Any of these will happen a lot faster than Subversion (and all your
other tools) being re-written to accommodate OS specific foibles.
-Matt
-----Original Message-----
From: Stuart Celarier [mailto:SCelarier@corillian.com]
Sent: Wednesday, December 14, 2005 8:57 AM
To: users@subversion.tigris.org
Subject: Re: Mixed case file names
Turaukar wrote:
>A simple hook could then convert all file names in uppercase to resolve
issues with mixed case.
Then performing a checkout or update from the repository, all the files
and folders in the working copy will be in uppercase. I'm not very keen
on that idea. At a minimum, we need to preserve case in the working
copy.
Wrt having a general mapping of repository file and folder names to
working copy file and folder names, how would you propose to guarantee
that the mapping is one-to-one (i.e., a bijection, being both an
injection and a surjection)? What would prevent the mapping from
(unwittingly) mapping cat.txt and dog.txt to mouse.txt? How would this
mapping mechanism scale, e.g., to hundreds or thousands of names? It
sounds like you are proposing to trade one problem for a much harder
problem.
Cheers,
Stuart
Stuart Celarier | Corillian Corporation
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 14 19:05:15 2005