SVN uses locks for exclusive checkout

?

SVN works in parallel by default, but the automatic merge is very messy. In the work of the Team, if there are some files that you want to exclusive checkout, you can use the special attributes of SVN.

?

?

?

The solution of subversion is to provide a mechanism to remind users that the file must be locked before editing. This mechanism is to provide a special attribute-SVN: Needs-lock. If this value exists, the file is read-only until the user locks the file. When you get a lock token (run SVN? Lock results), the file becomes read/write, when the lock is released, the file becomes read-only.

?

When you submit a project, the locked file is automatically displayed in the submission list.

?

For more information, see:

?

Http://tortoisesvn.net/docs/nightly/TortoiseSVN_zh_CN/tsvn-dug-locking.html

?

?

Operation:

Right-click a file and set its properties. (Not every file is exclusive)

?

?

?

?

?

?

?

?

?

?

Submit this file after setting. From then on, you need to obtain the lock before each file is edited.

?

?

If the file has been updated by another user, the latest version is forcibly obtained before the lock is obtained.

?

?

?

If the file is being checked out exclusively by another user, the lock acquisition fails.

?

?

?