On 03/28/2011 04:15 AM, Niels Möller wrote:
I take it I first need to scan the cvs log for all comitters and write a cvs-authors file (I remember I had some trouble with character set issues for the corresponding file when doing the hg migration for gmp. Should the names here be in the $LC_CTYPE charset, or always utf8?).
i'd do everything in utf8 myself, but then my LC_CTYPE always uses UTF-8 anyway. I don't know what the consequences are of doing things other ways.
Then, I'm not sure how to deal with branches, in particular, the -r and -o options. I'm not used to git, and with hg I also haven't used any "real" branches, I've just cloned the repository. I'm a bit scared by "You should never do any work of your own on the branches that are created by git cvsimport." in the man page.
I think I'd like to keep the possibility of doing cvs import more than once.
Meaning you want to update the cvs tree concurrently with the git repo?
This is doable, but it means that your git repo will need to be regularly rebased against the CVS tree. I've been doing this with the git repo i've published, but that's because the CVS tree is still in use. doing regular git cvsimports against an active CVS tree will make it more difficult for other people to develop against the git tree, which seems like it defeats one of the nice advantages of moving to a modern dvcs.
What command line did you use? What branches did you end up with?
I ran something like this:
cvs -d :pserver:anonymous@cvs.lysator.liu.se:/cvsroot/lsh \ co -d nettle lsh/nettle cd nettle git cvsimport
I ended up with no extra branches, though. Just a handful of tags. What sort of branches do you want to end up with?
--dkg