
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
68
|
Chapter 4: Branching and Merging
aren’t yet able to communicate with one another; that’s a feature planned beyond
Subversion 1.0.
*
Because svn switch is essentially a variant of svn update, it shares the same behav-
iors; 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
svn switch your working copy to the
branch, the local changes will remain. You can then test and commit them to the
branch.
Tags
Another common version control concept is a tag. A tag is just a snapshot of a
project in time. In Subversion, this idea already seems to be everywhere. Each reposi-
tory revision is exactly that—a snapshot of the filesystem after each commit.
However, people often want to give more human-friendly names to tags, like
release-1.0. And they want to make snapshots of smaller subdirectories of the file-
system. After all, it’s not so easy to remember that release-1.0 of a piece of software is
a particular subdirectory of revision 4822.
Switches and Updates
Have you noticed that the output of svn ...