[ft-devel] problems with CVS-git conversion

2009-03-03 Thread Werner LEMBERG
Folks, the `empty log message' problem in the conversion from CVS to git still bites me. It is far more trickier than expected :-( The steps I've suggested in a previous mail (using parsecvs, then `git format-patch' `git am') works in principle. However, tags created by parsecvs are lost.

Re: [ft-devel] problems with CVS-git conversion

2009-03-03 Thread David Turner
2009/3/3 Werner LEMBERG w...@gnu.org Would it make sense to first convert to GIT then later change the commit messages there. I tried that, and it doesn't work properly. Ah, can you tell me which problem exactly ? I could do the migration myself. By the way, I started documenting it at

Re: [ft-devel] problems with CVS-git conversion

2009-03-03 Thread Ralph Giles
On Tue, Mar 3, 2009 at 6:03 AM, Werner LEMBERG w...@gnu.org wrote:   . git format-patch   . editing commit messages in the *.patch files   . git am --rebasing --whitespace=nowarn *.patch works fine, however, it loses all tags created by parsecvs. Presumedly this is because changing the log