SVN 清理风险
SVN Cleanup Risks
据我了解，SVN cleanup 命令会释放工作副本的稳定锁定。
我可以在 SVN 更新命令之前将清理作为常规例程执行吗？
清理的风险是什么？
以下提到link:
http://jtdan.com/vcs/svn/tortoise/1.6/TortoiseSVN/tsvn-dug-cleanup.html
"If a Subversion command cannot complete successfully, perhaps due to
server problems, your working copy can be left in an inconsistent
state. In that case you need to use TortoiseSVN → Cleanup on the
folder. It is a good idea to do this at the top level of the working
copy.
Cleanup has another useful side effect. If a file date changes but its
content doesn't, Subversion cannot tell whether it has really changed
except by doing a byte-by-byte comparison with the pristine copy. If
you have a lot of files in this state it makes acquiring status very
slow, which will make many dialogs slow to respond. Executing a
Cleanup on your working copy will repair these “broken” timestamps and
restore status checks to full speed."
许多用户报告了清理速度缓慢的问题，这会消耗大量时间和内存，以防工作副本由于陈旧的锁而无法更新。
据我了解，SVN cleanup 命令会释放工作副本的稳定锁定。
我可以在 SVN 更新命令之前将清理作为常规例程执行吗？
清理的风险是什么？
以下提到link:
http://jtdan.com/vcs/svn/tortoise/1.6/TortoiseSVN/tsvn-dug-cleanup.html
"If a Subversion command cannot complete successfully, perhaps due to server problems, your working copy can be left in an inconsistent state. In that case you need to use TortoiseSVN → Cleanup on the folder. It is a good idea to do this at the top level of the working copy.
Cleanup has another useful side effect. If a file date changes but its content doesn't, Subversion cannot tell whether it has really changed except by doing a byte-by-byte comparison with the pristine copy. If you have a lot of files in this state it makes acquiring status very slow, which will make many dialogs slow to respond. Executing a Cleanup on your working copy will repair these “broken” timestamps and restore status checks to full speed."
许多用户报告了清理速度缓慢的问题，这会消耗大量时间和内存，以防工作副本由于陈旧的锁而无法更新。