[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: advice for a complicated import from CVS to SVN

From: Bob Proulx <bob_at_proulx.com>
Date: 2006-07-06 21:22:32 CEST

Alan Ezust wrote:
> Since the jedit repo is over 250mb, and contains a lot of crud we
> don't want to import the whole thing. Furthermore, the "plugins"
> directory contains many self-contained projects, each with their own
> tags, which have nothing to do with the tags in the jedit/ part of the
> tree.

Decide what you want to keep and what you want to throw away. After
you get a good inventory you can work from there.

> So my question is, what is the best way to import this into the
> sourceforge.net SVN repository? We assume it should be done on a
> project-by-project basis, but are there any tools that are best suited
> for the job? Any things we should keep in mind as we go through the
> conversion?

Look at the cvs2svn program. On my Debian system it is in its own
package. Here is the home page.


The cvs2svn program has many options that allow you to control what is
imported and what is not. You can also dump to an svn dump format and
then run the result through svn dump filters. I have had good result
using cvs2svn on a number of projects for a one time conversion. Give
that a try.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 6 21:25:14 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.