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

Re: Unusual behaviour of "svn mv" on directories

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-02-18 16:42:22 CET

Andy Parkins wrote:

> My question is: does "svn mv" of a directory alter the repository? If not -
> why do I need to run "svn update" after "svn mv" of a directory?

And here's a clear answer to your question: neither the Subversion
repository nor the Subversion working-copy have an "atomic move", which
is what you're expecting.

Instead, 'svn mv A B' is *exactly* the same as if you had run 'svn cp A
B; svn rm A'. When you do this in the working copy, you get a double
scheduling: B is new, scheduled for addition-with-history, and A is
scheduled for deletion. When you commit, the exact same thing happens
in the repository: B is created as a new object, copied from A, and
then A is deleted.

So what you're seeing in your recipe is a failure when you attempt to
commit the deletion of A. In your case, A is an out-of-date directory.

Hope this makes things clearer.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 18 16:42:59 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.