Alien-SVN
view release on metacpan or search on metacpan
src/subversion/doc/user/cvs-crossover-guide.html view on Meta::CPAN
<dt>Explanation:</dt>
<dd>Schedules a file or directory for addition or removal
to/from the repository. The repository will not be changed
until the user runs <tt>cvs commit</tt>, except for the case of
adding a directory, which immediately changes the repository.
Also, directories cannot be truly removed from the repository,
just emptied out. (<tt>cvs update -P</tt> will prune empty
directories from your working copy.)</dd>
</dl>
</td>
<td>
<dl>
<dt>Commands:</dt>
<dd><tt>$ touch foo.c</tt></dd>
<dd><tt>$ svn add foo.c</tt></dd>
<dd><tt>A foo.c</tt></dd>
<dd><tt> </tt></dd>
<dd><tt>$ mkdir new-dir</tt></dd>
<dd><tt>$ svn add new-dir</tt></dd>
<dd><tt>A new-dir</tt></dd>
<dd><tt> </tt></dd>
<dd><tt>$ svn rm bar.c</tt></dd>
<dd><tt>D bar.c</tt></dd>
<dd><tt> </tt></dd>
<dd><tt>$ svn rm old-dir</tt></dd>
<dd><tt>D old-dir/file1</tt></dd>
<dd><tt>D old-dir/file2</tt></dd>
<dd><tt>…</tt></dd>
<dt>Explanation:</dt>
<dd>Schedules a file or directory for addition or removal
to/from the repository. The repository will not be changed
until the user runs <tt>svn commit</tt>. The scheduled
operations are shown as <tt>A</tt> or <tt>D</tt> by <tt>svn
status</tt>, and <tt>svn revert</tt> can un-do the scheduling.
Directories really can be deleted (though as with all deleted
items, continues to exist in history.)</dd>
</dl>
</td>
</tr>
</table>
<dl class="bookref">
<dt>Book References:</dt>
<dd><a href="http://svnbook.red-bean.com/svnbook/ch03s05.html#svn-ch-3-sect-4.2">Make Changes to Your Working Copy</a></dd>
<dd><a href="http://svnbook.red-bean.com/svnbook/re01.html">svn add</a></dd>
<dd><a href="http://svnbook.red-bean.com/svnbook/re08.html">svn delete</a></dd>
</dl>
</div>
<!-- ==================================================================== -->
<div class="h2">
<h2 id="copying">Copying and moving</h2>
<p>Copy or move/rename a file or directory.</p>
<table class="sidebyside">
<tr>
<th>CVS</th>
<th>Subversion</th>
</tr>
<tr>
<td>
<dl>
<dt>Commands:</dt>
<dd>(not possible.)</dd>
<dt>Explanation:</dt>
<dd>Not possible, unless an administrator directly mucks with
RCS files in the repository. (And in that case, no history
records the act of copying or renaming.)</dd>
</dl>
</td>
<td>
<dl>
<dt>Commands:</dt>
<dd><tt>$ svn copy foo.c foo2.c</tt></dd>
<dd><tt>A foo2.c</tt></dd>
<dd><tt> </tt></dd>
<dd><tt>$ svn copy dir dir2</tt></dd>
<dd><tt>A dir2</tt></dd>
<dd><tt> </tt></dd>
<dd><tt>$ svn move bar.c baz.c</tt></dd>
<dd><tt>A baz.c</tt></dd>
<dd><tt>D bar.c</tt></dd>
<dd><tt> </tt></dd>
<dd><tt>$ svn move dirA dirB</tt></dd>
<dd><tt>A dirB</tt></dd>
<dd><tt>D dirA/file1</tt></dd>
<dd><tt>D dirA/file2</tt></dd>
<dd><tt>…</tt></dd>
<dt>Explanation:</dt>
<dd>The <tt>svn copy</tt> command schedules a file or directory
for addition to the repository, recording the "source" of the
copy. After committing, <tt>svn log</tt> on the copied item
will trace history back through the original copy-source. The
<tt>svn move</tt> command is exactly equivalent to running
<tt>svn copy</tt>, followed by an <tt>svn delete</tt> on the
copy-source: the result is a new item scheduled for addition
(with copy-history attached) and the original item scheduled for
deletion.</dd>
</dl>
</td>
</tr>
</table>
<dl class="bookref">
<dt>Book References:</dt>
<dd><a href="http://svnbook.red-bean.com/svnbook/ch03s05.html#svn-ch-3-sect-4.2">Make Changes to Your Working Copy</a></dd>
( run in 0.510 second using v1.01-cache-2.11-cpan-524268b4103 )