<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Sometimes You Just Need to Clean Up</title>
<link rel="stylesheet" type="text/css" href="styles.css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1" />
<style type="text/css">
body { background-image: url('images/draft.png');
background-repeat: no-repeat;
background-position: top left;
/* The following properties make the watermark "fixed" on the page. */
/* I think that's just a bit too distracting for the reader... */
/* background-attachment: fixed; */
/* background-position: center center; */
}</style>
<link rel="home" href="index.html" title="Version Control with Subversion [DRAFT]" />
<link rel="up" href="svn.tour.html" title="Chapter 2. Basic Usage" />
<link rel="prev" href="svn.tour.history.html" title="Examining History" />
<link rel="next" href="svn.tour.treeconflicts.html" title="Dealing with Structural Conflicts" />
</head>
<body>
<div xmlns="" id="vcws-version-notice">
<p>This text is a work in progress—highly subject to
change—and may not accurately describe any released
version of the Apache™ Subversion® software.
Bookmarking or otherwise referring others to this page is
probably not such a smart idea. Please visit
<a href="http://www.svnbook.com/">http://www.svnbook.com/</a>
for stable versions of this book.</p>
</div>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Sometimes You Just Need to Clean Up</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="svn.tour.history.html">Prev</a> </td>
<th width="60%" align="center">Chapter 2. Basic Usage</th>
<td width="20%" align="right"> <a accesskey="n" href="svn.tour.treeconflicts.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" title="Sometimes You Just Need to Clean Up">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="svn.tour.cleanup"></a>Sometimes You Just Need to Clean Up</h2>
</div>
</div>
</div>
<p>Now that we've covered the day-to-day tasks that you'll
frequently use Subversion for, we'll review a few administrative
tasks relating to your working copy.</p>
<div class="sect2" title="Disposing of a Working Copy">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="svn.tour.cleanup.disposal"></a>Disposing of a Working Copy</h3>
</div>
</div>
</div>
<p>Subversion doesn't track either the state or the existence of
working copies on the server, so there's no server overhead to
keeping working copies around. Likewise, there's no need to
let the server know that you're going to delete a working
copy.</p>
<p>If you're likely to use a working copy again, there's
nothing wrong with just leaving it on disk until you're ready
to use it again, at which point all it takes is an
<span class="command"><strong>svn update</strong></span> to bring it up to date and ready
for use.</p>
<p>However, if you're definitely not going to use a working
copy again, you can safely delete the entire thing using
whatever directory removal capabilities your operating system
offers. We recommend that before you do so you
run <strong class="userinput"><code>svn status</code></strong> and review any files
listed in its output that are prefixed with a
<code class="literal">?</code> to make certain that they're not of
importance.</p>
</div>
<div class="sect2" title="Recovering from an Interruption">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="svn.tour.cleanup.interruption"></a>Recovering from an Interruption</h3>
</div>
</div>
</div>
<p>When Subversion modifies your working copy—either
your files or its own administrative state—it tries to do
so as safely as possible. Before changing the working copy,
Subversion logs its intentions in a private <span class="quote">“<span class="quote">to-do
list</span>”</span>, of sorts. Next, it performs those actions to
effect the desired change, holding a lock on the relevant part
of the working copy while it works. This prevents other
Subversion clients from accessing the working copy mid-change.
Finally, Subversion releases its lock and cleans up its
private to-do list. Architecturally, this is similar to a
journaled filesystem. If a Subversion operation is
interrupted (e.g, if the process is killed or if the machine
crashes), the private to-do list remains on disk. This allows
Subversion to return to that list later to complete any
unfinished operations and return your working copy to a
consistent state.</p>
<p>This is exactly what <span class="command"><strong>svn cleanup</strong></span> does:
it searches your working copy and runs any leftover to-do
items, removing working copy locks as it completes those
operations. If Subversion ever tells you that some part of
your working copy is <span class="quote">“<span class="quote">locked,</span>”</span> run <span class="command"><strong>svn
cleanup</strong></span> to remedy the problem. The <span class="command"><strong>svn
status</strong></span> command will inform you about administrative
locks in the working copy, too, by displaying
an <code class="literal">L</code> next to those locked paths:</p>
<div class="informalexample">
<pre class="screen">
$ svn status
L somedir
M somedir/foo.c
$ svn cleanup
$ svn status
M somedir/foo.c
</pre>
</div>
<p>Don't confuse these working copy administrative locks with
the user-managed locks that Subversion users create when using
the lock-modify-unlock model of concurrent version control;
see the sidebar
<a class="xref" href="svn.advanced.locking.html#svn.advanced.locking.meanings" title="The Three Meanings of “Lock”">The Three Meanings of <span class="quote">“<span class="quote">Lock</span>”</span></a> for
clarification.</p>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="svn.tour.history.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="svn.tour.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="svn.tour.treeconflicts.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Examining History </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Dealing with Structural Conflicts</td>
</tr>
</table>
</div>
<div xmlns="" id="vcws-footer">
<hr />
<img src="images/cc-by.png" style="float: right;" />
<p>You are reading <em>Version Control with Subversion</em> (for
Subversion 1.8), by Ben Collins-Sussman, Brian W. Fitzpatrick,
and C. Michael Pilato.</p>
<p>This work is licensed under
the <a href="http://creativecommons.org/licenses/by/2.0/">Creative Commons Attribution License v2.0</a>.</p>
<p>To submit comments, corrections, or other contributions to the
text, please visit <a href="http://www.svnbook.com/">http://www.svnbook.com/</a>.</p>
</div>
</body>
</html>
distrib
>
Mageia
>
6
>
i586
>
media
>
core-updates
>
by-pkgid
>
d32d95698a59acd37b394f83dfc217c6
>
files
>
217
