I've been converting CVS working directories to SVN for a while now,
usually to recover locally modified files that haven't been checked in yet
(I've been creating "shelves" by just creating a new working directory,
which I realize is dangerous)
My method has been something similar to the following:
(1) check out the SVN folder at the equivalent revision that the CVS
folder was most recently updated. The revisions must have identical
(2) adjust the properties on your files, especially eol-style. When I
converted my repository via cvs2svn, it left out all the eol-styles. I
did apply them later, but checking out an old revision probably doesn't
have these properties set which could really mess things up on the next
(3) Copy the .svn folders in each of the folders in your hierarchy into
your CVS working directory (probably want to make a backup of your CVS WD
first) You now have a CVS/SVN mixed working directory, please run SVN
status and CVS status to ensure that they both flag the same file
(4) Do an SVN update. This will bring your WC up to date as well as
fixing the property thunking you did in step 2. If you are using
TortoiseSVN, then the icon overlays should properly show changed files
(5) When you are done, delete the CVS folders in your directory.
From: Gary Thomas [mailto:firstname.lastname@example.org]
Sent: Thursday, August 18, 2005 10:47 AM
To: Patrick Burleson
Cc: email@example.com; Janelle Janish
Subject: Re: Convert cvs working copy to svn working copy?
On Thu, 2005-08-18 at 13:07 -0400, Patrick Burleson wrote:
> On 8/18/05, Bob Proulx <firstname.lastname@example.org> wrote:
> > Yes. The tool is called cvs2svn. You can read about it in the book
> > here:
> > http://svnbook.red-bean.com/en/1.1/apas11.html
> > For one example, on my Debian machine it may be installed with the
> > following command:
> > apt-get install cvs2svn
> > Then used like this:
> > cvs2svn --fs-type=fsfs -s /path/to/new-svn-repos
> Unfortunately that's not what's being asked for. That would convert a
> CVS repository to a SVN one.
> As for converting a working copy, I don't know of any tool that does
> that. The CVS and SVN working copy formats are very different. I don't
> think it would be wise to try and convert them.
> Is there a reason, other than not wanting to do it, to not just
> recheckout? It should be a fairly starightforward process and you'll
> only have to do it once. Whereas some conversion tool might mess up
> and force you to do it over and over and over.
In addition, unless he actually converts his CVS repository to
an SVN one, what good does it do to have a SVN working copy?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Aug 18 20:18:58 2005
- application/x-pkcs7-signature attachment: smime.p7s