Version Control with Subversion

This is the Title of the Book, eMatter Edition

Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.

30

|

Chapter 3: Guided Tour

svn move foo bar

This command is exactly the same as running svn copy foo bar; svn delete

foo

. That is, bar is scheduled for addition as a copy of foo, and foo is scheduled

for removal.

svn move does not create intermediate directories.

Examine Your Changes

Once you’ve finished making changes, you need to commit them to the repository,

but before you do so, it’s usually a good idea to take a look at exactly what you’ve

changed. By examining your changes before you commit, you can make a more accu-

rate log message. You may also discover that you’ve inadvertently changed a file, and

this gives you a chance to revert those changes before committing. Additionally, this

is a good opportunity to review and scrutinize changes before publishing them. You

can see exactly what changes you’ve made by using

svn status, svn diff, and svn

revert

. You will usually use the first two commands to find out what files have

changed in your working copy, and then perhaps the third to revert some (or all) of

those changes.

Subversion has been optimized to help you with this task, and is able to do many

things without communicating with the repository. In particular, your working copy

contains a secret cached pristine copy of each version controlled file within the .svn

area. Because