freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: David Turner
Subject: Re: [ft-devel] problems with CVS->git conversion
Date: Tue, 3 Mar 2009 14:09:40 +0100

Hi Werner,

2009/3/3 Werner LEMBERG <address@hidden>

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?

Would it make sense to first convert to GIT then later change the commit messages there.
I believe it's going to be much easier, and to be honest, I'm unsure that updating the original
CVS messages is going to be very useful.
 


   Werner


_______________________________________________
Freetype-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/freetype-devel


reply via email to

[Prev in Thread] Current Thread [Next in Thread]