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

Re: Changing Case / svn move

From: Ryan Schmidt <subversion-2006q2_at_ryandesign.com>
Date: 2006-05-31 17:27:37 CEST

On May 31, 2006, at 15:59, Markus KARG wrote:

> As we all know, changing case of a filename (e. g. using svn move)
> results in problems on Windows.
> One main issue is that svn move internally is implemented as svn
> copy, svn delete: This duplicates the filename before removing the
> old one.
> Since Windows in near future will not support case sensitive file
> systems, I want to ask why not changing the command sequence svn
> move is doing to "svn copy OLD --> TMP, svn delete OLD, svn copy
> TMP --> NEW, svn delete NEW". Sure I know that this doubles the
> execution time of the move command, but hey, how often are we doing
> a rename? Also, this could be framed by "if (isWindows &&
> oldName.equalsIgnoreCase(newName)", which should not eat too much
> time.
> What do you think?
> Actually SVN is great, but the case problem in Windows is really
> ugly and this would be an acceptable solution.

The problem affects Mac OS X just as much as Windows.

It has nothing to do with Windows or Mac OS X, in fact; it has to do
with the default filesystems commonly used on those two operating
systems, which are case-insensitive.

Windows and Mac OS X both have the ability to use case-sensitive
filesystems and thereby avoid the issue; it's just not the default.
Similarly, Linux and friends can use case-insensitive filesystems and
thereby run into the issue, but that's not the default there.

That doesn't help with your situation or really answer your question,
I know, I just wanted to set the record straight about those things.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 31 17:29:09 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.