1 <?xml version="1.0" encoding="UTF-8"?>
\r
2 <!DOCTYPE sect1 SYSTEM "../../../dtd/dblite.dtd">
\r
3 <sect1 id="tsvn-dug-cleanup">
\r
4 <title>Cleanup</title>
\r
6 <primary>cleanup</primary>
\r
9 If a Subversion command cannot complete successfully, perhaps
\r
10 due to server problems, your working copy can be left in an
\r
11 inconsistent state. In that case you need to use
\r
13 <guimenu>TortoiseGit</guimenu>
\r
14 <guimenuitem>Cleanup</guimenuitem>
\r
16 on the folder. It is a good idea to do this at the top level
\r
17 of the working copy.
\r
20 Cleanup has another useful side effect. If a file date changes
\r
21 but its content doesn't, Subversion cannot tell whether it has
\r
22 really changed except by doing a byte-by-byte comparison with
\r
23 the pristine copy. If you have a lot of files in this state it
\r
24 makes acquiring status very slow, which will make many dialogs
\r
25 slow to respond. Executing a Cleanup on your working copy will
\r
26 repair these <quote>broken</quote> timestamps and restore
\r
27 status checks to full speed.
\r
30 <title>Use Commit Timestamps</title>
\r
32 Some earlier releases of Subversion were affected by a bug
\r
33 which caused timestamp mismatch when you check out with
\r
34 the <guilabel>Use commit timestamps</guilabel> option
\r
35 checked. Use the Cleanup command to speed up these
\r