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

Re: Renaming only case on Windows

From: Daniel Schlyder <daniel_at_dascdev.net>
Date: 2003-08-31 02:40:59 CEST

[31.08.2003 01:44:18] Jack Repenning:
> Well, you skipped prety quick from "the easy things that don't work" to
> "really huge things that, yes, do work."

Okay. :)

> There are one or two middle-sized ways to get the effect:

> The quickest way to make this approach work is to use a filesystem that
> understands what you're trying to say (a case-sensitive file system).

Well, switching from Windows to an OS that supports such a filesystem certainly
sounds like a "really huge thing". :) Or are you suggesting Windows can be made
to support case-sensitive filenames?

>>$ svn mv foo temp
>>$ svn mv temp Foo --force

> In between your two "svn mv" commands, you could "svn commit" (as suggested
> by the messages). You'd also need an "svn update", I think.

Yeah, I considered that, but wanted to avoid the extra revision.

>>$ svn mv file:///repos/trunk/foo file:///repos/trunk/Foo -m "Renamed file."
>>$ svn up

> Here, "rm foo" between the svn commands would have made it all work. Or, in
> general, when you see "obstructed update," you can respond by removing or
> renaming the obstructing file. This is another case of SVN's care not to
> trash anything of yours.

I couldn't get this to work. 'svn up' fails with error:

Restored foo
svn: Obstructed update
svn: failed to add file 'Foo': object of the same name already exists

Thanks for helping,
Daniel Schlyder

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 31 02:42:10 2003

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