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

Re: encouraging users to switch

From: Bryan Donlan <bdonlan_at_hikari.afraid.org>
Date: 2005-02-05 04:07:07 CET

John Kristian wrote:
> Can you recommend a way to encourage users to execute `svn switch` after
> a branch is moved?
> I plan to move a branch that has many working copies, which were checked
> out by many users. I'll tell the users to run `svn switch`, but I
> expect some stragglers will neglect to do so. If they run `svn update`,
> their working copies will be deleted (because I deleted the old branch).
> This will be annoying: it will cost them time to delete their working
> copies and then re-create new ones (after switching). Most will be
> startled to see the deletions, and some will waste time and energy
> figuring out that they need to switch. (But it won't do any lasting
> harm that I can think of.)
> It would be better if `svn update` from the old branch had no effect on
> users' working copies, and gave a warning message like:
> This branch has moved.
> Try again, after executing `svn switch <new branch> <working copy>`.

This doesn't seem to be a problem:

$ svn info
Path: .
URL: file:///home/bdonlan/svntest/testrepo/branch
Repository UUID: bef702d5-54ef-0310-a8c6-8f58bf3a6737
Revision: 1
Node Kind: directory
Schedule: normal
Last Changed Author: bdonlan
Last Changed Rev: 1
Last Changed Date: 2005-02-04 22:03:18 -0500 (Fri, 04 Feb 2005)

$ svn ls file:///home/bdonlan/svntest/testrepo
$ svn rm file:///home/bdonlan/svntest/testrepo/branch -m ''

Committed revision 2.
$ svn up
svn: Cannot replace a directory from within
$ cd ..
$ svn up testwc
svn: Cannot replace a directory from within

Received on Sat Feb 5 04:09:23 2005

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.