From: Marko Mäkelä (marko.makela_at_hut.fi)
Date: 2007-01-11 22:38:08
On Thu, Jan 11, 2007 at 09:46:49PM +0100, Ullrich von Bassewitz wrote:
>
> On Thu, Jan 11, 2007 at 10:20:00PM +0200, Marko Mäkelä wrote:
> > I switched from CVS (after almost 10 years of using it) to Subversion in
> > late 2005, so I didn't have to deal with the potential horrors of the
> > original BDB-backed Subversion.
>
> Do you have experience with converting CVS repositories to SVN?
I haven't converted any CVS repository to SVN myself, but at work we
had one CVS repository that I believe was converted with cvs2svn
<http://cvs2svn.tigris.org/>.
The challenge with the conversion is how to detect which commits belong
together (because CVS commits each modified file separately while
Subversion commits the whole tree at once).
My colleague who did the conversion at work said that there is some way
to specify a threshold. For example, if files have been committed less
than n minutes apart, they belong to the same commit (or changeset).
Of course, this rule won't work at all times. You could have committed
unrelated small changes to several files quickly, or you might have been
interrupted for a few hours while you were typing change log messages
for the individual files in a large "cvs commit".
> I've been thinking about moving to SVN at home, because of the many
> advantages, but I fear loosing my version history.
If I were you, I'd give cvs2svn a try (fiddle with the parameters until
the outcome is satisfactory) and keep a backup of the original repository
just in case.
Well, I must confess that I didn't generally use any version control
for private projects until last year. I have used RCS, CVS, BitKeeper
and Subversion at work. I've had the least trouble with Subversion.
Marko
Message was sent through the cbm-hackers mailing list
Archive generated by hypermail pre-2.1.8.