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

Re: [Issue 1585] Deltified dumps for archival and schema conversion

From: <kfogel_at_collab.net>
Date: 2004-06-21 19:39:47 CEST

Mikhail Terekhov <termim@charter.net> writes:
> It is Dell Precision 650 - 2 cpu (2.66GHz), 1G memory , local IDE WD
> 250 GB drive,
> OS - SuSE-9.1 Linux.

I'm surprised, but unfortunately, I don't have enough hardware to try
this myself :-(. Sorry. (Speed of the drive might be relevant, but
given the rest of the system, I doubt you bought a slow drive! :-) )

However, even if the conversion takes 10 days (or 20, or whatever),
that's not prohibitive. It effectively just means you delay your
group's switchover by that many days:

   1. Convert CVS repository at time T to a dumpfile.
   2. Start loading the dumpfile into an SVN repository.
   3. While it's loading, continue working in CVS.
   4. When the load is done, take all commits in CVS since time T, and
      replay them into the new SVN repository.
   5. From now on, all work happens in Subversion.

Obviously, there's some scripting to do here, and it would be nice if
cvs2svn.py made this easier (by taking a date-range specifier, for
example). However, the main thing is that even long conversion times
needn't prevent switching to Subversion.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 21 21:04:22 2004

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

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