Re: Filename case

Jeff Lanzarotta wrote:

> There's no real solution for the first issue, unless we introduce the
> notion of a "case-insensitive" repository and forced some kind of
> case-insensitive behaviour in all working copies. That's a huge change
> and won't happen any time soon, if ever.

I can think of reasons besides development effort not to put this in the
server, but I'd like to make the case for handling this as a special
case in the client.

My ideal behaviour would be for the client to silently ignore any case
differences between the server and the client. A pre-commit script would
still be needed to keep the repository clean, but always kicking up
errors is inconvenient for developers and interrupts the workflow.

This is a serious disruption because on Windows it's uncommon but not
rare for a tool to change the case of filename without telling you. In
particular, one of the tools in Visual Studio .NET which we use to
generate database scripts is particularly random about filename case,
enough that this problem as exhibited in CVS (well, and bad unicode
handling) has forced us to maintain these scripts outside the
repository, which is suboptimal.

-- 
Joseph Lunderville, Software Developer
Haden Software Inc.
604-693-2323
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org