svn update — Update your working copy.
svn update brings changes from the
repository into your working copy. If no revision is given,
it brings your working copy up-to-date with the
HEAD revision. Otherwise, it
synchronizes the working copy to the revision given by the
--revision option. As part of the
synchronization, svn update also
removes any stale locks (see the section called “Sometimes You Just Need to Clean Up”) found in the
For each updated item, it prints a line that starts with a character reporting the action taken. These characters have the following meaning:
A character in the first column signifies an update to the actual file, while updates to the file's properties are shown in the second column.
As with most subcommands, you can limit the scope of
the update operation to a particular tree depth using the
--depth option. Alternatively, you can
use the --set-depth option to set a new
“sticky” working copy depth on the update
target. Currently, the depth of a working copy directory
can only be increased (telescoped more deeply); you cannot
make a directory more shallow.
--revision (-r) REV --depth ARG --set-depth ARG --force --quiet (-q) --no-ignore --incremental --diff3-cmd CMD --editor-cmd ARG --accept ARG --username USER --password PASS --no-auth-cache --non-interactive --config-dir DIR --ignore-externals --changelist
Pick up repository changes that have happened since your last update:
$ svn update A newdir/toggle.c A newdir/disclose.c A newdir/launch.c D newdir/README Updated to revision 32.
You can also “update” your working copy to an older revision (Subversion doesn't have the concept of “sticky” files like CVS does; see Appendix B, Subversion for CVS Users):
$ svn update -r30 A newdir/README D newdir/toggle.c D newdir/disclose.c D newdir/launch.c U foo.c Updated to revision 30.
If you want to examine an older revision of a single file, you may want to use svn cat instead—it won't change your working copy.