Re: cvs2git initially, then git cvsimport

Hi Michael,

> cvs2git and "git cvsimport" use different mechanisms for inferring changesets from the CVS history, and they would probably not match up on the boundary.
> Please note that "git cvsimport" is not very reliable, and it can silently produce incorrect content (even of the HEAD revision).  The "ISSUES" section of its manpage lists some of its known bugs.

Thanks for that definite answer. So basically, the only reliable way is the one linked from the cvs2git documentation, i.e. running cvs2git once a day e.g. There is a point I do not understand though: won't cvs2git generate different sha1 at each run? It will make rebasing the working branch more difficult, won't it?

Best wishes,

Luc Bourhis

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2991289

To unsubscribe from this discussion, e-mail: [[email protected]].