<?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>Converting a Repository from CVS to Subversion</title><link rel="stylesheet" href="styles.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="Version Control with Subversion" /><link rel="up" href="svn.forcvs.html" title="Appendix B. Subversion for CVS Users" /><link rel="prev" href="svn.forcvs.auth.html" title="Authentication" /><link rel="next" href="svn.webdav.html" title="Appendix C. WebDAV and Autoversioning" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Converting a Repository from CVS to Subversion</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="svn.forcvs.auth.html">Prev</a> </td><th width="60%" align="center">Appendix B. Subversion for CVS Users</th><td width="20%" align="right"> <a accesskey="n" href="svn.webdav.html">Next</a></td></tr></table><hr /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="svn.forcvs.convert"></a>Converting a Repository from CVS to Subversion</h2></div></div></div><p>Perhaps the most important way to familiarize CVS users with
Subversion is to let them continue to work on their projects
using the new system. And while that can be somewhat
accomplished using a flat import into a Subversion repository of
an exported CVS repository, the more thorough solution involves
transferring not just the latest snapshot of their data, but all
the history behind it as well, from one system to another. This
is an extremely difficult problem to solve that involves
deducing changesets in the absence of atomicity, and translating
between the systems' completely orthogonal branching policies,
among other complications. Still, there are a handful of tools
claiming to at least partially support the ability to convert
existing CVS repositories into Subversion ones.</p><p>The most popular (and likely the most mature) conversion
tool is cvs2svn (<a class="ulink" href="http://cvs2svn.tigris.org/" target="_top">http://cvs2svn.tigris.org/</a>), a
Python script originally created by members of Subversion's own
development community. This tool is meant to run exactly
once: it scans your CVS repository multiple times and attempts
to deduce commits, branches, and tags as best it can. When it
finishes, the result is a either a Subversion repository or a
portable Subversion dumpfile representing your code's history.
See the website for detailed instructions and caveats.</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="svn.forcvs.auth.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="svn.forcvs.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="svn.webdav.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Authentication </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix C. WebDAV and Autoversioning</td></tr></table></div></body></html>
