Dean Roehrich <Dean.Roehrich at sun.com> writes: > On Fri, Jun 20, 2008 at 02:49:15PM -0400, Hua Huang wrote: >> 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. > > Begin at the Mercurial homepage. You'll find a link to a page about > converting repositories. > > http://www.selenic.com/mercurial/wiki/ > > There are a few tools which can convert from CVS to Mercurial. A lot depends > on how well cvsps interprets your particular CVS repo.
In trying to form a reply to this (Dean's was better, so I hit delete), I tried using hg's convert extension against the cvs repositories I happened to have handy (all small, none complex), and it worked out pretty well. As Dean said, much likely depends on the complexity of your repository, and how well cvsps can deal with that. I think that's the way to go. (unless someone with more experience of them advises otherwise). The tool used to go from TeamWare to Mercurial for onnv is basically entirely dependent upon various hooks used by onnv-gate, it's far from generic (it won't even work with most other teamware gates, never mind other SCMs). -- Rich
