Svn is so simple 2 -- svn commands in linux

Svn is so simple 2 & mdash; svn command in linux 1. run the file checkout to the local directory svncheckoutpath (path is the directory on the server), for example: svncheckoutsvn: // 192.168.1.1/pro/domain abbreviation: svnco2, add to version library... svn is so simple 2 -- svn command in linux 1. run the file checkout 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 a new file svn add file to the version library, for example, svn addtest. php (add test. php) svn add *. php (add all php files in the current directory) 3. submit the modified files to the version Library svn commit-m "LogMessage" [- N] [-- no-unlock] PATH (if the lock is selected, 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 svn update-r m path to a specific version. for example, if svn update does not have a directory, all files in the current directory and subdirectory 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: svn up 6. view the file or directory status 1) svn status path (the status of the files and subdirectories under the Directory, the normal status 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 (display file and subdirectory status) the first column remains the same, the second column shows 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 the file 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 then svn ci-m 'delete test file'. we recommend that you use this abbreviation: svn (del, remove, rm) 8. view the 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 the details of the file svn info path, for example, svn info test. php 10. Differences: svn diff path (compare the modified file with the basic version) for example: svn diff test. phpsvn diff-r m: n path (for version m and version n Differences) for example: svn diff-r 200:201 test. php abbreviation: svn di 11. merge the differences between the two versions to the current file svn merge-r m: n path for example: svn merge-r 200:205 test. php (merge the differences between version 200 and 205 to the current file, but there are usually conflicts, you need to handle it) 12. SVN helps svn helpsvn help ci ------------------------ and above are common commands, below are some commonly used files and directories in the version Library: svn ls 14. create a new directory under version control: 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 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 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 will not restore the deleted directory 16. the code library URL changes svn switch (sw): updates 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 the files on the server will be merged with local files. This is a method that maps a work copy to a branch or tag in the same repository. 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 changes ), however, when the working copy is still mapped to the same directory in the same warehouse, use this command to update the correspondence between the working copy and the warehouse. 17. resolve the conflict svn resolved: remove the "conflict" status of the directory or file of the working copy. Usage: resolved PATH... Note: subcommands do not follow the syntax to resolve conflicts or remove conflicting tags. they only remove conflicting 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)