Re: Clarifying "invalid tag signature file" error message from git filter-branch (and others)

From: Jakub Narebski <jnareb@gmail.com>
Date: Dec 12, 2008, 16:53 UTC
Message-ID: <m3bpvhgws3.fsf@localhost.localdomain>
In-Reply-To: <87zlj1hd0r.fsf@rho.meyering.net>

Jim Meyering <jim@meyering.net> writes:

Show 11 quoted lines

> 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