The svk switch command transforms an
existing working copy into a different branch. While this
command isn't strictly necessary for working with branches, it
provides a nice shortcut to users. In our earlier example,
after creating your private branch, you checked out a fresh
working copy of the new repository directory. Instead, you can
simply ask Subversion to change your working copy of
/calc/trunk to mirror the new branch
$ cd calc $ svk info | grep URL URL: http://svk.example.com/repos/calc/trunk $ svk switch http://svk.example.com/repos/calc/branches/my-calc-branch U integer.c U button.c U Makefile Updated to revision 341. $ svk info | grep URL URL: http://svk.example.com/repos/calc/branches/my-calc-branch
After “switching” to the branch, your working copy is no different than what you would get from doing a fresh checkout of the directory. And it's usually more efficient to use this command, because often branches only differ by a small degree. The server sends only the minimal set of changes necessary to make your working copy reflect the branch directory.
The svk switch command also takes a
-r) option, so you
need not always move your working copy to the “tip”
of the branch.
Of course, most projects are more complicated than our
calc example, containing multiple
subdirectories. Subversion users often follow a specific
algorithm when using branches:
Copy the project's entire “trunk” to a new branch directory.
Switch only part of the trunk working copy to mirror the branch.
In other words, if a user knows that the branch-work only needs to happen on a specific subdirectory, they use svk switch to move only that subdirectory to the branch. (Or sometimes users will switch just a single working file to the branch!) That way, they can continue to receive normal “trunk” updates to most of their working copy, but the switched portions will remain immune (unless someone commits a change to their branch). This feature adds a whole new dimension to the concept of a “mixed working copy”—not only can working copies contain a mixture of working revisions, but a mixture of repository locations as well.
If your working copy contains a number of switched subtrees from different repository locations, it continues to function as normal. When you update, you'll receive patches to each subtree as appropriate. When you commit, your local changes will still be applied as a single, atomic change to the repository.
Note that while it's okay for your working copy to reflect a mixture of repository locations, these locations must all be within the same repository. Subversion repositories aren't yet able to communicate with one another; that's a feature planned beyond Subversion 1.0.
Because svk switch is essentially a variant of svk update, it shares the same behaviors; any local modifications in your working copy are preserved when new data arrives from the repository. This allows you to perform all sorts of clever tricks.
For example, suppose you have a working copy of
/calc/trunk and make a number of changes to
it. Then you suddenly realize that you meant to make the
changes to a branch instead. No problem! When you svk
switch your working copy to the branch, the local
changes will remain. You can then test and commit them to the