SVN for Mac Considerations

For other uses of SVN, you can enter in the terminal: SVN help

Principle:

In terms of jargon too blunt, simple can be understood as a storage of things (resources) of the warehouse, he has an automatic management function, the resources you stored into a copy, you can delete and add, use the command line to tell him what you want to do. Here is the main point of attention in the team combat
SVN for Mac Considerations:
• Upload code required (a complete project), need to submit a static library file, cancel the selection of ignored files and upload
• After uploading the code, delete the extra profile.
Check out files need to confirm again whether the static library files are updated to download locally, with extra compiled files, delete redundant compilation files, determine the static library file all download, try run. If no problem, the code has been successfully updated to local.
commit need upodata before, commit need updata again. Try run is required for each updata. Make sure the code runs successfully.
• Before creating a new file, you need to upodata, try run, create the file after the problem, submit it in a timely manner, and then Updata Again,try run. Every updata requires a try run and ensures that the code runs successfully.

• Resolve conflicts not all issues can be clicked resolve solve the problem. You need to view the conflicting files for conflicting reasons.
• The most important thing is not to submit a local git file. In order to change the configuration of the project Info.plist the premise is not to submit any files other than the code (plainly said to be. M and. h). But: you must submit the configuration file you changed when you have changed the profile and run the support that requires configuration files.
• Never submit half of the code. Never after the commit after the Updata, found the local code error, after the modification does not commit, such errors are low-level errors, not explained.
• If you find that you have submitted the wrong file, please revert it immediately. Don't ask what, low-level mistakes do not explain.
• For files that you have not made any changes to. What you need is to ignore his submission. Rather than a full submission of a brain. It must be clear that all the code you are submitting is the entire code you have changed. Instead of SVN prompting you to submit the code. It is possible that you have changed something by mistake (low-level error does not explain)
• Delete files need to remember to delete unnecessary folders, this is a good habit, need you remember
• Code classification must be clear, submit the file must be submitted to the appropriate folder, easy to manage and find
• The most annoying thing about submitting your code is to never submit it until you get off the clock. Are you sure that what you write one day is not impulsive to others?! Please follow the function point to write a little, submit a little. This facilitates management and reduces unnecessary conflicts.
• Do not arbitrarily change the code to unregister others, especially when you are unsure of the function, to reduce the level of error
• Create your own classes, delete them in a timely manner, and reduce the redundancy of your code.
• The above is my summary of SVN, basically in accordance with the normal use is not a problem, if the low-level error occurs once is negligence, that every time I was enough. For the problem of wire break and lock code, it is important to note that the code is often not updated, but loses the connection, needs to be found in the show in find him, and pull into the project.

SVN for Mac Considerations