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

Re: Possible svn bug?

From: Attila BODY <compi_at_freemail.hu>
Date: 2004-04-07 20:26:32 CEST

On Wed, 2004-04-07 at 19:47, Ben Collins-Sussman wrote:
> On Wed, 2004-04-07 at 12:27, Attila BODY wrote:
> There's no bug here. Subversion doesn't have true moves. It implements
> moves as copies and deletes.
> That means that 'svn mv foo bar' is exactly the same as running 'svn cp
> foo bar; svn rm bar'.
> After running the command, 'svn status' will show two things
> "scheduled": bar will be scheduled for addition (with historical
> information attached), and foo will be scheduled for deletion. When you
> run 'svn commit', the addition and deletion will actually happen in the
> repository, and then in your working copy.
> When you then run 'svn log bar', you'll be able to see that bar was
> copied from foo, i.e. is a continuation of the same line of history.
Yes, you are right but it still seems to be a bug in my case.

Last time I've moved some documentation directories from my development
tree to my docs tree, to speed source code checkouts. If I check the
logs, I can't find lines beginning vith 'D' only beginning with 'A' in
the log of that specific commit.

It looks like if I did not make a move, but a copy. I had (and was able
to) delete old directories manually with "svn del". This is why I still
suspecting a bug here. I made mv, and the "delete" part of the
copy-then-delete nature of mv command did not happened.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 7 20:30:37 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.