tisdagen den 29 april 2008 19.15.06 skrev Lars Alexander Noschinski: > ... hack away ... > git-cvsimport -i -r cvs -kk -v -d $CVSREPOS > git-rebase cvs # If work was done in the meantime > git-cvsexportcommit -cpuv $COMMIT # Multiple times, if necessary > git-cvsimport -i -r cvs -kk -v -d $CVSREPOS > git-checkout -b master cvs # commit ids are changed now > > As far as I am concerned, this works fairly well, accept when for any > reason a line containing a CVS keyword (e.g. $Id$) is contained in a > changeset. In this case, patching fails, and I have to investigate why it > fails, eventually just copying the old version from the cvs repository. > > Would it be possible to add an option to cvsexportcommit to detect such > killed keywords and ignore them? Sure, but is it necessary? If the cvs checkout you use is checked out with -kk there shouldn't be any problem. If not, start by thinking up a few testcase for inclusion in t9200-git-cvsexportcommit.sh that illustrates the problem. Then we can change cvsexporcommit until the new tests pass. -- robin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
