Project Manager: Import new project to SVN server SVN import [path] URL programmers often do (the project manager occasionally also co, or up): The first down code: SVN co URL [PATH] first into the outermost project folder commit code: SVN ci--u Sername= account--password= password-m ' Submit today's results ' Update code: SVN up to see what local files are a\m\d\? (Ps:a represents the new, m for the change, d for the deletion, the file has not been added to version management, SVN does not recognize him) if SVN st is empty, then the local file and server are exactly the same. SVN St lists the current folder and which files are within the SVN version control SVN List adds a new file to the local version Control library (PS: After adding, can commit) SVN add PATH removes the file from the local version control library (PS: After removal, can commit) SVN del fallback (PS: can only rollback files enumerated in SVN St) s vn revert path fallback to a version (PS: In the code has been commit to the server, you can use this) SVN update-r version number PATH Note: When the commit code is prompted out of date, indicates that a file on the server has a version number greater than a local file The version number is high, you need to manually resolve the conflict manually to resolve the conflict steps: 1>svn up 2> DF, see 1 where the conflict points in the 2> hit p, indicating the meaning of manual resolution 3>SVN will be in the directory of the conflict file, generate 3 files, low version files, high-version files, MI NE file Low-version files: Local changes to the code before the mine file: Local changes to the code of the High-level files: SVN server code on the role of the 3 files, just used to refer to, the real need to change the conflict file, after the conflict file, after the end to knock SVN resolved, said The conflict has been modified, delete the 3 reference documents.
IOS SVN terminal instructions
