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. I'm now going to investigate whether parsecvs can be edited so that its two-staging operation can be stopped after the first stage. My idea is that after reading all CVS repository files, the commits are written as editable diff files (with some additional `commands' to transport tags and similar meta stuff). parsecvs already does this, but currently uses a binary format (or something in compressed form). Then I can check all those files, possibly fixing the commit messages. The last step is continuing with parsecvs's second stage to convert all those diffs to a git repository. On the other hand, a cvs2patch tool might already exist which emits a CVS repository as a set of patches. Any ideas or links? Werner _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel