Jim Meyering <jim@xxxxxxxxxxxx> writes: > I used parsecvs, probably with git-master from the date of > the initial conversion (check the archives for actual date). > That was long enough ago that it was almost certainly before > git-mktag learned to be more strict about its inputs. > > James, since you're about to rewrite the history, you may want to > start that process from a freshly-cvs-to-git-converted repository. > > I'm not very happy about using parsecvs (considering it's not > really being maintained, afaik), so if the git crowd > can recommend something better, I'm all ears. The page you might want to consult is http://git.or.cz/gitwiki/InterfacesFrontendsAndTools There you have listed git-cvsimport, which uses cvsps to extract patchset, is in git, and is as far as I know the only tool that allow incremental import; parsecvs which requires access to *,v files you use; cvs2svn (cvs2git) which have learned fast-import format and can be used to import (fast) CVS repositories, but incremental import (difficult that it is) is only in plans, AFAIK. So I would recommend trying cvs2svn / cvs2git. -- Jakub Narebski Poland ShadeHawk on #git -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
