CVS conversion and branches

[David I.]

Greg Ward-17 wrote:
> 
> I'm surprised Michael Haggerty hasn't jumped in to point out that CVS
> conversions based on cvsps, like Mercurial's, are inherently flawed
> and doomed to failure.  (Michael is the maintainer of cvs2svn, so he
> knows a thing or two about extracting useful info from CVS.)
> 
> The usual advice in such cases is to give cvs2svn a try.  Or rather,
> use cvs2git (which is included with cvs2svn) to generate git
> fastimport dumps, then load those into Mercurial with hg-fastimport.
> The catch is that I have been hacking on hg-fastimport recently.  It
> should be better than it was, but it's extremely bleeding edge.  It
> passes its tests, but I have yet to try it on a real-world CVS repo
> and the resulting fastimport dumps.
> 

To follow up on my attempts to convert our CVS repo, I have finally gotten
cvs2svn working. However, to do so I installed it on our CVS server which is
a Solaris 10 box. I had to compile/install gdbm, Python 2.5.1, and svn to
get cvs2svn to work. 

So far, it appears to have sucessfully converted several release branches to
SVN where the hg convert didn't work. I'm in the process of figuring out
which tags & branches I want to keep, and which ones to ignore. 

David
-- 
View this message in context: http://www.nabble.com/CVS-conversion-and-branches-tp23371675p24378644.html
Sent from the Mercurial mailing list archive at Nabble.com.