CODEWITHSUNDEEP
svntortoisesvn
user3165438
user3165438

Reputation: 2661

SVN Cleanup Risks

As far as I understand, the SVN cleanup command releases stable locking form working copy.

Can I execute the cleanup as a regular routine before SVN update command?
What are the risks of cleanup?

Upvotes: 2

Views: 1962

Answers (1)

Kuntal Shaw
Kuntal Shaw

Reputation: 1395

Mentioned in the following 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."

Many users have reported about slow cleanup which consumes a lot of time and memory in case the working copy does not update due to stale locks.

Upvotes: 1

Related Questions