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

Re: Suggestion for cvs->svn converter

From: Karl Fogel <kfogel_at_collab.net>
Date: 2001-07-13 17:46:42 CEST

"Jim Whitehead" <ejw@cse.ucsc.edu> writes:
> I worked at Continuus for a summer and did some development on their
> Migration tool, which sucked code into the Continuus repository from SCCS or
> RCS repository files. One thing that was very important in the tool was to
> provide a status indicator that gave an estimate of the time remaining in
> the conversion activity. Since it took appx. 1 second per revision (in
> 1994), importing a large project could take hours. It was handy for people
> to know that they could fire off the import, than come back later in N
> hours. Machines are much faster now, but still, I imagine the cvs->svn
> converter might still take O(minutes) to finish.
> Logging was also important, since it allowed the admin. in charge of the
> import to know which revisions experienced problems during the import
> operation.

+1 on both suggestions.

Really huge, multi-gigabyte repositories, like the RedHat (Cygnus) GNU
tools codebase, are going to take noticeable time to convert -- we are
at least talking about minutes, if not hours. A progress indicator
and log are necessities.

> I suppose it would also be handy if the conversion utility used a plug-in
> architecture, so people could develop conversion plug-ins for multiple
> version control systems, rather than just limit the utility to CVS.

Sure, just depends how much extra work it is.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:33 2006

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