The role of SVN clean up

When SVN is updated locally, the user cancels because some operations interrupt the update, such as insufficient disk space. May cause local files to be locked. The workaround for this scenario is generally:

1. You can use SVN clean up to clear the lock.

2, if the directory is not locked, the system prompts for a directory lock, need to go to the previous level or root directory to clear.

3. If the root directory is not clean, the general approach is to find another directory to re-checkout. Sometimes, however, there may be some locally modified files in the SVN directory that have not yet been submitted to the SVN server, and the re-checkout need to be aware of the backup of the local files, and do not force overwriting content that is modified by others on the server.

4. If you feel that the 3rd kind of trouble, you can consider such a method. In fact, SVN lock will generate a file named lock in. SVN (hidden file), find all, manually delete. Then try the update again, and you may be prompted that a. base file is inaccessible. Find it, delete the relevant file or the directory in which it is located, and update it again. The workload is much smaller.

Reprinted from http://blog.csdn.net/scyatcs/article/details/21942289

The role of SVN clean up