On 9/20/07, Zack Grossbart <zgrossbart@novell.com> wrote:
> I have run into a Subversion issue that is causing me some trouble. I have
> a simple test case. I have a working copy that looks like this:
>
> test.txt
> mydir
>
> I check out two different copies of these files. I then make a change to
> the test.txt file in my first working copy (I added the line "this is my
> change") and check it in. I then issue a move command in the second working
> copy that looks like this:
>
> svn mv test.txt mydir
>
> I then update my second working copy and I get the version of test.txt in
> the old location as an unversioned file. I then check in my second working
> copy and I get the following output:
>
> Adding mydir\test.txt
> Deleting test.txt
>
> The problem is that I didn't get the latest version of the test.txt file.
> Just an unversioned copy of the test.txt file in the location before the
> move. When I update my first working copy the test.txt file is moved, but
> it lost the change made to the file. The revision of the file with the
> "this is my change" line is gone. I never deleted it, but it disappeared on
> its own. The only way I can get it back is to update the directory it used
> to be at to a revision when it used to be there.
>
> Does anyone have any idea what is going on? Is there any way I can prevent
> this? Should I be sending this to a general Subversion instead of a
> Subclipse list?
That is how Subversion works in this situation. See this blog post for more:
http://markphip.blogspot.com/2006/12/subversion-moverename-feature.html
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Sep 21 02:39:31 2007