11.07.2015 Views

Version Control with Subversion - Login

Version Control with Subversion - Login

Version Control with Subversion - Login

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Subversion</strong> Complete ReferenceNamesvn switch — Update working copy to a different URL.Synopsissvn switch URL[@PEGREV] [PATH]switch --relocate FROM TO [PATH...]DescriptionThe first variant of this subcommand (<strong>with</strong>out the --relocate option) updates your workingcopy to point to a new URL—usually a URL that shares a common ancestor <strong>with</strong> yourworking copy, although not necessarily. This is the <strong>Subversion</strong> way to move a workingcopy to a new branch. If specified, PEGREV determines in which revision the target is firstlooked up. See the section called “Traversing Branches” for an in-depth look at switching.If --force is used, unversioned obstructing paths in the working copy do not automaticallycause a failure if the switch attempts to add the same path. If the obstructing path isthe same type (file or directory) as the corresponding path in the repository, it becomesversioned but its contents are left untouched in the working copy. This means that an obstructingdirectory's unversioned children may also obstruct and become versioned. Forfiles, any content differences between the obstruction and the repository are treated like alocal modification to the working copy. All properties from the repository are applied to theobstructing path.As <strong>with</strong> most subcommands, you can limit the scope of the switch operation to a particulartree depth using the --depth option. Alternatively, you can use the --set-depth optionto set a new “sticky” working copy depth on the switch target. Currently, the depth of aworking copy directory can only be increased (telescoped more deeply); you cannot makea directory more shallow.The --relocate option causes svn switch to do something different: it updates yourworking copy to point to the same repository directory, only at a different URL (typically becausean administrator has moved the repository to another server, or to another URL onthe same server).Alternate namesChangesswWorking copyAccesses repositoryOptionsYes--accept ARG--depth ARG--diff3-cmd CMD--force--ignore-externals--quiet (-q)--relocate288

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!