Open source softwares - Apache SVN(Sub Version)

Back to Course

Lesson Description

Lession - #1557 SVN Update Process

#### Name ```plaintext svn update( up>
— Update your working copy. ```   #### Synopsis ```plaintext svn update( PATH.>
```   #### Description svn update brings changes from the depository into your workingcopy.However, it brings your working copy up to date with the HEAD modification, If no modification is given. else, it synchronizes the working copy to the modification given by the-- modification(- r>
option. As part of the synchronization, svn update also removes any stale locks( see the section called “ occasionally You Just Need to Clean Up ”>
set up 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  B  Broken lock( third column only>
  D  Deleted  U  Updated  C  Conflicted  G  Merged  E  Existed  A character in the first column signifies an update to the actual file, whereas updates to the file's properties are shown in the alternate column. Lock information is printed in the third column.  As with most subcommands, you can limit the scope of the update operation to a particular tree depth using the-- depth option. Alternately, you can use the-- set- depth option to set a new “ sticky ” working copy depth on the update target.    #### Options * \-- accept ACTION * \-- changelist(-- cl>
ARG * \-- depth ARG * \-- diff3- cmd CMD * \-- editor- cmd CMD * \-- force * \-- ignore- externals * \-- parents * \-- quiet(- q>
* \-- revision(- r>
REV * \-- set- depth ARG svn update is also the primary mechanism used to configure sparse working copies. When used with the-- set- depth, the update operation will omit or reenlist individual working copy members by modifying their recorded ambient depth to the depth you specify( fetching information from the depository as necessary>
. See the section called “ Sparse Directories ” for further about sparse directories. You can update multiple targets with a single invocation, and Subversion won't only gracefully skip any unversioned targets you give it, but as of Subversion1.7 will also include apost-update summary of all the updates it performed   ```plaintext

``` ```plaintext cd my- projects svn update * Updating' calc' Ubutton.c Uinteger.c Updated to revision 394. Skipped'tempfile.tmp' Updating' paint' Apalettes.c Ubrushes.c Updated to revision 60. Updating' ziptastic' At revision 43. Summary of updates Updated' calc' to r394. Updated' paint' to r60. Updated' ziptastic' to r43. Summary of conflicts Skipped paths 1 ```