Re: git-cvsimport fuzzy commit log matching?

On Tue, Dec 23, 2008 at 10:53:42AM -0200, Martin Langhoff wrote:

What you could do is

 1 - run cvsps with export to a file (I've posted in this list how to
run it exactly as cvsimport does)
 2 - post-process cvsps ouput with perl (there's a parser already in
cvsimport ;-) )
 3 - run cvsimport with the post-processed file

Or postprocess the imported git tree as others have suggested.

Instead of post-processing I hacked cvsps.  It already has a different
way to detect changesets when running in --bkcvs mode, and re-using that
one for ptools works great.