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

Re: filename case renaming issue (FAQ A.2.4)

From: Douglas Stetner <dstetner_at_bigpond.net.au>
Date: 2004-03-25 23:54:25 CET

On 25/3/04 at 18:03 (+0800), sean@moss-pultz.com (Sean Moss-Pultz)
wrote:

>Hopefully someone can help clarify what I'm doing wrong here....
>
>1) rename using TortoiseSVN menu rename from "test.h" to "Test.h_". 2)
>commit 3) rename using TortoiseSVN menu rename from "Test.h_" to
>"Test.h". 4) commit 5) update local copy (for grins) 6) move to
>_another_ workstation and run update command. Note: If I run update
>from the same workstation I will not get the following error message.
>7) get error message "Failed to to add file '<....path...>/Test.h':
>object of the same name already exists"
>

Sounds like subversion is trying to be 'smart' and roll the two changes
into one, thereby trying to move test.h directly to Test.h since it is
probably not required to take a file through each revision in order to
update it.

It makes sense, in a way, as if you are updating a file from rev 1 to
rev 100 you would not want it to go through all 99 revs to update....

Try to update to the file with a -rXX to get the middle name (Test.h_)
and then update to the next.

Note I am not an svn expert, so I could be all wrong 8-)

Doug

-- 
Douglas Stetner                                   <dstetner@bigpond.net.au>
"In those days spirits were brave, the stakes were high, men were real men,
women were real women and small furry creatures from Alpha Centauri were
real small furry creatures from Alpha Centauri."
                                                  - Douglas Adams
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 23:55:03 2004

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.