A working copy of SVN is just a copy with the .svn folder in each folder and subfolder of the project you are working on. They are used to track any pending changes to the project content. These .svn folders can be deleted, leaving the project files with the latest changes that have not yet been made to the central SVN repository / server.
TortoiseSVN 1.7 uses these .svn folders in the sense that they are no longer compatible with older versions of TortoiseSVN. In no case will this affect the Subversion server and repository when deleting local copies of .svn .
My solution outlined here ensures that everything that has not yet been made from a damaged / damaged copy that has been deleted from its .svn folders can be copied to a new working copy pulled out of TortoiseSVN 1.7, which will be completed later. The reason for a corrupted copy must be deleted from its .svn folders because when it is copied to a new blank copy, the βbeautifulβ .svn folders in the blank copy will not be overwritten so as to preserve the last good condition of the blank copy from the server.
source share