• Name

    svn update – Update your working copy.

    Synopsis

    svn update [PATH…]

    Description

    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 working copy.

    For each updated item, it prints a line that starts with a character reporting the action taken. These characters have the following meaning:

    A

    Added

    D

    Deleted

    U

    Updated

    C

    Conflicted

    G

    Merged

    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.

    Alternate Names

    up

    Changes

    Working copy

    Accesses Repository

    Yes

    Options

    --revision (-r) REV
    --non-recursive (-N)
    --quiet (-q)
    --no-ignore
    --incremental
    --diff3-cmd CMD
    --username USER
    --password PASS
    --no-auth-cache
    --non-interactive
    --config-dir DIR
    --ignore-externals
    

    Examples

    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.
    

    Tip

    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.


    The Version Control with Subversion book is licensed under the Creative Commons Attribution License v2.0.
    To submit comments, corrections, or other contributions to the text, please visit http://www.svnbook.com.