I believe we'll want to do a reexport with a cvsps containing mast's patches first as well.
Ah, yes. Because of the coming migration to git at Roxen, I've been hacking a bit the last months on cvsps and git-cvsimport to make them work decently (I started on it before I noted the bit at the end of git-cvsimport(1) enumerating all its serious faults). I got most things sorted out now, including vendor branch mirroring etc.
I've pushed my patches to srb's repo at pike-git.lysator.liu.se:cvsps.git/.git
If cvsps/git-cvsimport is used for the pike repo then I strongly suggest using my patched tools, but I got the impression that other tools are used since it's based on Comstedts svn export, right?
Btw, in my conversion of (mainly) the Roxen Webserver repo, I've done some other things which I think are nice. One is to include the cvs revisions in old commit messages, since cvs commits might refer to other commits that way. E.g:
commit dbe28d2 Author: Henrik Grubbström grubba@grubba.org Date: Fri May 15 14:30:26 2009 +0200
First go at automatic database backups. Currently disabled by ENABLE_DB_BACKUPS.
[subtabs.pike 1.18, DBManager.pmod 1.86]
server/config_interface/dbs/subtabs.pike | 21 + server/etc/modules/DBManager.pmod | 595 ++++++++++++++++++++++++++++-- 2 files changed, 577 insertions(+), 39 deletions(-)
Another is to make tag names look nicer by converting "_" to "-" or ".", e.g. "roxen_5_0_366" in cvs becomes "roxen-5.0.366" in git.
I can of course provide my scripts and stuff for that if someone wants it.