SVN default parallel work, but it does very dregs automatically merged. Team work, if indeed there are some files may want to check out the exclusive use SVN special properties.
Subversion solution for this problem is to provide a mechanism to remind the user must lock the file before you start editing, this mechanism is to provide a special property --svn: needs-lock. When this value, unless you lock the file, or the file has been read-only. When a lock token (the result of running svn lock), the file becomes read-write, when the lock is released, the file becomes read-only.
When submitting projects, locked files will automatically appear in the commit list.
More information:
http://tortoisesvn.net/docs/nightly/TortoiseSVN_zh_CN/tsvn-dug-locking.html
Operating Screenshot:
Right-click a file, setting a property. (Not everyone wants exclusive file)
After setting the submission of this document, since then, every time the file before editing need to acquire the lock.
If the file has been updated by other users, the acquisition will be forced to obtain the latest version before lock
If this file is exclusively checked out by another user, acquire the lock failure
