Summary: svn commands in Linux

Svn (subversion) is a version management tool that has emerged in recent years. svn servers run in two ways: independent servers and apache. The two methods have their own advantages and disadvantages. In either way, various commands are required. In this article, haohtml provides us with common and uncommon svn commands in Linux.

1. checkout the file to the local directory.

Svn checkout path (path is the directory on the server)

For example, svn checkout svn: // 192.168.1.1/pro/domain Abbreviation: svn co

2. Add new files to the version Library

Svn add file

For example, svn add test. php (add test. php) svn add *. php (add all php files in the current directory)

3. Submit the modified file to the version library.

Svn commit-m "LogMessage" [-N] [-- no-unlock] PATH (if you choose to keep the lock, use the-no-unlock switch)

For example, svn commit-m "add test file for my test" test. php Abbreviation: svn ci

4. Lock/unlock

Svn lock-m "LockMessage" [-- force] PATH

For example, svn lock-m "lock test file" test. phpsvn unlock PATH

5. Update to a specific version.

Svn update-r m path

For example, if there is no directory after svn update, all files in the current directory and sub-directories are updated to the latest version by default. Svn update-r 200 test. php (restores the file test. php In the version library to version 200) svn update test. php (updated, synchronized in the version library. If an expiration prompt is prompted during submission, it is because of a conflict. You need to update the file, modify the file, clear svn resolved, and then submit commit.

6. view the file or directory status

1) svn status path (the State of the files and subdirectories under the directory. The normal state is not displayed)

? : Not under svn control; M: The content is modified; C: A conflict occurs; A: It is scheduled to be added to the version Library; K: it is locked]

2) svn status-v path (displays the status of files and subdirectories)

The first column remains the same, the second column displays the working version number, and the third and fourth columns show the last modified version number and modifier.

Note: svn status, svn diff, and svn revert commands can be executed without a network, because svn is locally deployed. svn retains the original copy of the local version.

Abbreviation: svn st

7. delete an object

Svn delete path-m "delete test fle"

For example, svn delete svn: // 192.168.1.1/pro/domain/test. php-m "delete test file" or directly svn delete test. php and svn ci-m 'delete test file'. We recommend that you use this abbreviation: svn (del, remove, rm)

8. View logs

Svn log path

For example, svn log test. php displays all the modification records of this file and changes to its version number.

9. View File details

Svn info path

Example: svn info test. php

10. Differences

Svn diff path (compare the modified file with the basic version)

Example: svn diff test. php

Svn diff-r m: n path (differences between version m and version n)

For example: svn diff-r 200:201 test. php Abbreviation: svn di

11. Merge the differences between the two versions into the current file.

Svn merge-r m: n path

For example, svn merge-r test. php (merge the differences between version 200 and version 205 to the current file, but there are usually conflicts. You need to handle them)

12. SVN help

Svn help

Svn help ci

--------------------------

The above are common commands. Below are a few

--------------------------

13. List of files and directories in the version Library

Svn list path

Displays all files and directories in the path directory that belong to the version library.

Abbreviation: svn ls

14. Create a new directory under Version Control

Svn mkdir: Create a new directory under version control.

Usage: 1. mkdir PATH...

2. mkdir URL...

Create a version control directory.

1. Each directory specified by the working copy PATH will be created on the local end and added to the new

Scheduling to wait for the next submission.

2. Each directory specified with a URL is created by submitting it to the repository immediately.

In both cases, all the intermediate directories must exist in advance.

15. Restore local modification

Svn revert: restore the original unchanged working copy file (recover most local modifications ). Revert:

Usage: revert PATH...

Note: The sub-commands do not access the network and will release the conflict. But it won't be restored.

Deleted directory

16. code library URL change

Svn switch (sw): update the working copy to different URLs.

Usage: 1. switch URL [PATH]

2. switch-relocate from to [PATH...] 1. update your working copy and map it TO a new URL. The behavior is similar TO "svn update" and

Merge files on the server with local files. This maps the work copy to a branch or tag in the same warehouse.

Method.

2. Rewrite the URL metadata of the working copy to reflect the changes on the simple URL. When the root URL of the Repository changes

(For example, the solution name or host name change), but the working copy is still mapped to the same directory in the same repository.

This command updates the correspondence between the working copy and the warehouse.

17. Conflict Resolution

Svn resolved: the "Conflict" Status of directories or files that remove working copies.

Usage: resolved PATH...

Note: subcommands do not follow the syntax to resolve conflicts or remove conflicting tags. They only remove conflicting tags.

Related files, and then allow the PATH to be submitted again.

18. output the content of the specified file or URL.

Svn cat target [@ version]… If a version is specified, search for it 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 result can be submitted)

Connection: http://blog.haohtml.com/archives/8323