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

Re: svn up can loose local modifications

From: <kfogel_at_collab.net>
Date: 2004-05-07 20:40:59 CEST

SteveKing <steveking@gmx.ch> writes:
> As the subject indicates, the 'svn up' command can revert all local
> modifications on a case insensitive filesystem like Windows and OSX
> have.
> Example:
> /wc/File1.txt
> Edit this file with an editor. Then save the modifications. Now, some
> editors on Windows change the case of the filename. Either to all
> lowercase or all uppercase. Especially some older editors change the
> case to all uppercase. That means we get
> /wc/FILE1.TXT
> now, if we do an 'svn up', the file will get reverted to
> /wc/File1.txt
> and all local modifications are gone.

That's weird. Why doesn't 'svn up' notice that the file (since it's
the "same" file) is locally modified, and merge the repos changes if
any? (If there are no repos changes, nothing should happen, right?)

I don't have easy access to a case-insensitive system. Can you debug
into the update editor, perhaps? I'm very puzzled by the behavior.

> I already added this to the issue 667
> (http://subversion.tigris.org/issues/show_bug.cgi?id=667) but I wanted
> to point this out on the mailing list too since the issue tracker
> isn't suited for discussions.

By the way, regarding your comment in the issue about setting the
repository case-insensitive: this protection could be completely
implemented in a hook script. I don't think anyone's posted such a
script, but it wouldn't be that hard to write (I've seen them for CVS,
for example).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 8 00:45:33 2004

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.