we did try a couple of other tools as well.. Let me try to dig some of the notes (hopefully I can find them) to see what worked and what didn't in terms of importing all branches.
I know for sure we didn't import all branches but just the HEAD in our case As soon as I find the missing information, I will get back with the above data in that case. thanks Tushar > It seems cvsps doesn't care much for our CVS repo, but I haven't had a > chance to try tailor yet. (Originally we were also considering git, > and cvs2git worked perfectly.) Where you able to import all of your > CVS branch history into a single mercurial repository with tailor? > This has been our main problem with cvs -> hg conversions so far. > > cheers, > robert > > On Jun 20, 2008, at 13:51 , Tushar Desai wrote: > >> We migrated the entire code base including history from CVS --> >> Mercurial >> >> After investigating several tools, Tailor was selected as it could >> handle importing the whole CVS history, and our tests showed that the >> import was successful. >> >> For more info, see >> http://www.selenic.com/mercurial/wiki/index.cgi/Tailor >> >> Thanks >> Tushar >> x84886 >> >>> Dear scm-migration-dev, >>> >>> Lustre group (formally known as Clustre File System Inc, which was >>> bought >>> by Sun Last year) has been using CVS as the SCM tool. In order to >>> move in >>> the same direction as the ON community, we also plan on switching >>> from CVS >>> to Mercurial. >>> >>> One of the big technical challenge is how we can do this without losing >>> the branch history (file revision/history). How do you manage to >>> preserve the >>> file revision/history from Teamware -> Mercurial? Can the same >>> mechanism apply to >>> the CVS->Mercurial transition? We hope you can share the expertise >>> in your team >>> and help us to address this issue. Really appreciate it. >>> >>> -Hua >>> >>> >>> _______________________________________________ >>> scm-migration-dev mailing list >>> scm-migration-dev at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/scm-migration-dev >>> >> >
