[M3devel] --> Git

[Dragiša Durić]

You probably all know differences between theory and practice. In theory, there are none. In practice - a lot of them! :)

I have identified three main ways to convert CVS to Git. 

One looked most promising as it is bidirectional (and incremental) - using git cvsimport. I did this one, and its result is at github right now. But - it is not good. Some files show wrong version in HEAD. git cvsimport depends on old version of cvsps, and those cvsps people probably released newer version for some reason(s)… As long as I don’t want to dive into cvsps / git cvsimport source codes, no solution there. And I really do not have that kind of interest and/or time.

Ok, no incremental… This is where I tried cvs2git. It works well but it does not map authors (svn2git does, but although cvs2git comes from same team, features are not in concert). There is some arcane way proposed, but I lost trust when I saw svn2git from same team supports authors file, but cvs2git does not. Not big issue, but I had that in first try so I tried third way.

Third way is cvs2svn, and then git svn clone. Results look good, esp. after applying some after processing proposed bu Git people. 

One proposal there is to not convert whole repository history. My idea is to convert from just before 5.8.6 was released (July 2010). Does anybody have something against this? I will still keep original CVS repo, and SVN conversion results (where all history is accessible). If there is oposition, I will spend some more CPU time and make full history available through Git. There are around 10000 svn revisions before July 2010, and total of 12752 as of today.

Please advise :)

TIA,
dd

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20140817/1a14ccec/attachment-0001.sig>