Product SiteDocumentation Site

4.5. The Basic Subversion Work Cycle

(Adapted from Version Control with Subversion under Creative Commons Attribution License v2.0.)
Subversion has numerous features, options, and bells and whistles, but on a day-to-day basis, odds are that you only use a few of them. In this section we run through the most common things you might find yourself doing with Subversion in the course of a day's work.
The typical work cycle looks like this:
Update your working copy
Make changes
Examine your changes
Possibly undo some changes
Resolve Conflicts (Merge Others' Changes)
Commit your changes

4.5.1. Update Your Working Copy

When working on a project with a team, you want to update your working copy to receive any changes made since your last update by other developers on the project. Use svn update to bring your working copy into sync with the latest revision in the repository.
$ svn update
U  foo.c
U  bar.c
Updated to revision 2.
In this case, someone else checked in modifications to both foo.c and bar.c since the last time you updated, and Subversion has updated your working copy to include those changes.
When the server sends changes to your working copy via svn update, a letter code is displayed next to each item to let you know what actions Subversion performed to bring your working copy up-to-date. We cover the meaning of these letters shortly. Exercise - Get Updates From the Sample Repository

Update your working copy of the TOS repo. Has anything changed?