Detailed description of common SVN commands under linux command line

1. Checkout files to a local directory under the Linux command line

SVN checkout Path (path is a directory on the server)

Example: SVN checkout Svn://192.168.1.1/pro/domain

Shorthand: SVN Co

2. Add new files to the repository from the Linux command line

SVN Add File

Example: SVN add test.php (add test.php)

SVN add *.php (Add all php files in the current directory)

3. Submit the changed files to the repository under the Linux command line

SVN commit-m "LogMessage" [-n] [--no-unlock] PATH (use –no-unlock switch if hold lock is selected)

Example: SVN commit-m "Add test file for my test" test.php

Shorthand: svn ci

4. Locking/unlock under Linux command line

SVN lock-m "Lockmessage" [--force] PATH

Example: SVN lock-m "lock test File" test.php

SVN unlock PATH

5. Update to a version of Linux command line

SVN update-r m path

For example:

SVN update If there is no directory behind it, the default is to update all files in the current directory and subdirectories to the latest version.

SVN update-r test.php (Restore the file test.php in the repository to version 200)

SVN update test.php (updated, sync in Repository.) If the prompt expires at the time of submission, it is because of the conflict, you need to update, modify the file, then clear the SVN resolved, and then commit the commit)

Shorthand: SVN up

6. View file or directory status under Linux command line

1) SVN status path (status of files and subdirectories under directory, normal status not shown)

"?: not in SVN control; M: Content modified; C: conflict; A: Scheduled to be added to Repository; K: Locked"

2) SVN status-v path (show file and subdirectory status)

The first column remains the same, the second column shows the work version number, and the third and fourth columns show the last modified version number and the modified person.

Note: The SVN status, SVN diff, and SVN revert three commands can be executed without a network, because SVN retains the original copy of the local version in. svn.

Shorthand: SVN St

7. Delete files under linux command line

SVN delete path-m "Delete test Fle"

Example: SVN delete svn://192.168.1.1/pro/domain/test.php-m "Delete test file"

Or go directly to svn delete test.php and then svn ci-m ' delete test file ', which we recommend using this

Shorthand: SVN (del, remove, RM)

8. View logs under Linux command line

SVN log path

For example: SVN log test.php shows all changes to this file, and its version number

9. View file details under linux command line

SVN info Path

Example: SVN info test.php

10, the Linux command line comparison difference

SVN diff path (compares the modified file to the base version)

Example: SVN diff test.php

SVN diff-r m:n Path (difference between version m and version N)

Example: SVN diff-r 200:201 test.php

Shorthand: SVN di

11. Merge the differences between the two versions into the current file under the Linux command line

SVN merge-r m:n Path

For example: SVN merge-r 200:205 test.php (the difference between version 200 and 205 is merged into the current file, but generally conflicts occur and need to be addressed)

12, Linux command line under SVN help

SVN help

SVN help CI

The above is a common command, the following write a few common

13. List of files and directories under the Linux command line repository

SVN list Path

Displays all files and directories belonging to the repository under the path directory

Shorthand: SVN ls

14. Create a new directory under version control under the Linux command line

SVN mkdir: Create a new directory under the included version control.

Usage: 1, mkdir PATH ...

2. mkdir URL ...

Create a version-controlled directory.

1. Each directory specified in the working copy PATH will be created on the local side and added to the new schedule for the next commit.

2. Each directory specified in the URL will be created by submitting it to the repository immediately. In both cases, all intermediate directories must exist beforehand.

15. Restore local modifications under Linux command line

SVN revert: Restores the original unchanged working copy file (restores most of the local modifications). Revert

Usage: revert PATH ...

Note: The notebook command will not access the network and will release the conflicting condition. But it does not restore the deleted directory

16. Code base URL change under linux command line

SVN switch (SW): Updates the working copy to a different URL.

Usage: 1, switch URL [PATH]

2. Switch–relocate from to [PATH ...]

1. Update your working copy to map to a new URL that behaves like SVN update and merges the file on the server with the local file. This is the method that corresponds a working copy to a branch or tag in the same warehouse.

2, rewrite the working copy of the URL metadata to reflect the simple URL changes. When the repository's root URL changes (such as scheme name or hostname change), but the working copy is still mapped to the same directory as the same repository, use this command to update the corresponding relationship between the working copy and the warehouse.

17. Resolve conflicts under Linux command line

SVN resolved: Removes the "conflicting" status of the working Copy's directory or file.

Usage: Resolved PATH ...

Note: The book command does not resolve the conflict by syntax or remove the conflict token; it simply removes the conflicting file and then allows PATH to commit again.

18, the Linux command line output the content of the specified file or URL.

SVN cat Target [@ VERSION] ... If a version is specified, the lookup starts from the specified version.

SVN cat-r PREV filename > filename (PREV is the previous version, you can also write a specific version number so that the output can be submitted)

Original address: http://os.51cto.com/art/200908/143157.htm

Detailed description of common SVN commands under linux command line