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

RE: what does svn move "do" to currently checked out branches

From: Gavin Lambert <gavinl_at_compacsort.com>
Date: 2007-01-26 07:34:26 CET

Quoth noisrevbussresu.20.stripes@antichef.net <>:
> I have a project that has changed it's name, I want to:
> svn svn+ssh://..../old-project-name svn+ssh://..../new-project-
> name
> What happens when someone who has old-project-name/branches/
> issue-12417 attempts to merge it to new-project-name/trunk ?
> Will it follow the rename and know that a change to old-project-name/
> branches/issue-12417/foo.c should be merged to new-project-name/
> branches/trunk/foo.c ?

I'm not 100% certain what it will do, but I'm fairly sure that it will
*not* follow the rename.

If I recall correctly, what it will do is something like this:

  - if you're moving/renaming a folder *below* the topmost folder that
someone has already checked out:
    - any commits by them involving that folder will fail until they do
an update
    - the update will see the move as a delete followed by an add, which
means that they will download lots of file data
    - if they had modified files in the folder being deleted, then the
modified files will be left alone (still in the "wrong" folder, and no
longer under version control), and the latest checked-in versions will
show up in the "new" folder.

  - if you're moving/renaming a folder *above* (or equal to) the topmost
folder that they've checked out:
    - they will not be able to commit or update until they execute an
"svn switch" to the new location

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 26 07:34:56 2007

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.