On 8/3/07, Michael Haggerty <mhagger@xxxxxxxxxxxx> wrote: > [I set followup-to users@xxxxxxxxxxxxxxxxxx, since this has nothing to > do with git.] > > Jon Smirl wrote: > > On 8/3/07, Patwardhan, Rajesh <rajesh.patwardhan@xxxxxxxxxx> wrote: > >> Hello Michael, > >> I will explain a scenario (we are passing thru this right now) > >> 1) you have 10 years worth of cvs data. > >> 2) We want to move to svn. > >> 3) The repository move should be in such a way that the development does > >> not get hampered for any 1 work day. > >> 4) We have atleast 4 major modules in cvs which takes about 30 - 40 > >> hours each for conversion currently. > > > > There are known ways (that haven't been implemented) to get the 40 hr > > number down to 1/2 hour. Would that be a better approach than doing > > incremental imports? > > Jon, I would like very much to hear how you propose to get an 60-fold > speed increase in cvs2svn. I've never heard of any plausible way to > accomplish anything even close to this. > > Please note that the user wants to convert to Subversion, not git. But > even converting to git, I don't think that such speeds are possible > without massive changes that would include processing everything in RAM > and switching large parts of cvs2svn from Python to a compiled language. Make a bulk importer for SVN like git-fastimport. I measured some SVN imports and the bulk of the time was spent forking off SVN. Before git-fast import it would have taken git two weeks to import Mozilla CVS. > > Michael > > -- Jon Smirl jonsmirl@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
