Jon Smirl wrote:
> I lost power this morning while the city decided to move the telephone
> pole in front of my house. That killed the import that had been
> running for five days.
If an import was taking five days then almost assuredly the result
would not be something that you would want to be using for real.
There is something undesireable about it such as the duplication
possibility or something. You would almost certainly have needed to
convert it again after detecting the problem and dealing with it.
Basically what I am saying is that after five days I would have killed
it whether the power was running or not. You did not lose anything
that was not already lost.
As one example, when the GCC project converted from CVS to SVN the
conversion was started and stopped and started and stopped a number of
times until the conversion time got down to something reasonable. You
would not want to bring gcc offline for weeks waiting for a
conversion. It needs to happen in a short enough time to be
reasonable.
Daniel Berlin wrote on the gcc list way back on 6-Mar-2005:
> Due to some massive speedups i've implemented in cvs2svn, the full gcc
> repo, including all non-broken tags (more in a moment), is now
> available. It would have taken ~7 days before, and now it takes less
> than 2 (it's almost completely disk bound now, and my 7200rpm disks just
> aren't fast enough apparently :P)
Which I read as being that with large projects it will probably take a
few turns to get a good result out of the tools. With small projects
I have not had any trouble with cvs2svn. But large projects may need
special handling.
Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 14 08:48:08 2006