journaled filesystem. If a Subversion operation is interrupted (e.g., if the process is killed or if the machine crashes), the logfiles remain on disk. By reexecuting the logfiles, Subversion can complete the previously started operation, and your working copy can get itself back into a consistent state. And this is exactly what svn cleanup does: it searches your working copy and runs any leftover logs, removing working copy locks in the process. If Subversion ever tells you that some part of your working copy is "locked," this is the command that you should run. Also, svn status will display an L next to locked items: $ svn status L somedir M somedir/foo.c $ svn cleanup $ svn status M somedir/foo.c Don't confuse these working copy locks with the ordinary locks that Subversion users create when using the lock-modify-unlock model of concurrent version control; see the sidebar "The Three Meanings of "Lock"" on page 75 for clarification. Summary Now we've covered most of the Subversion client commands. Notable exceptions are those dealing with branching and merging (see Chapter 4) and properties (see "Prop-