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

Re: Case-sensitivity and Windows

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2003-06-30 03:22:11 CEST

Julian Foad wrote:

> Garrett Rooney wrote:
>> John Barstow wrote:
>>> I recently had a developer add a file twice, with slight differences in
>>> case. This of course causes problems with updates and checkouts;
>>> since the filesystem is case-insensitive.
>> There are just too many filesystem dependent special cases that we
>> don't bother trying to handle them.
> Unfortunately if Subversion is going to be useful on Windows it is going
> to have to play nicely with case-insensitivity and other file system
> restrictions. Not only Windows; almost every platform has some
> different file naming restrictions. I think Subversion will need, to
> some extent, generalised support for file system restrictions:
> Is this file name valid (on file system X)?
> Is this file name the same as that one (on file system X)?
> etc.
> and a policy or choice of policies for when to enforce these
> restrictions (at check-in time, or check-out/update time; per repository
> or per directory; etc.)
> The details of how it can best do this will no doubt be thrashed out on
> this list in the near future.

I'm unclear why this has to be part of Subversion itself. It seems like
project policy on what filenames are appropriate are just that: project
policy, no different from policy regarding use of branches and tags or
any number of other things. All this stuff can be dealt with via a
pre-commit hook if needed. Now if someone wants to write such a hook
script, more power to them, but I don't see how this is more complex
than that.

For the record, Perforce, which is quite 'useful on Windows', does not
have any such seat belts. I had a problem when my company first started
using Perforce with a file named prn.c. The server was on a win32
machine at the time, and windows interpreted the prn as 'printer', which
caused no end of grief.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 30 03:22:59 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.