From: Hannu Koivisto <azure@iki.fi>
Date: Wed, 27 Dec 2006 21:03:15 GMT
Subject: git-cvsimport doesn't support the default branch mechanism?
Message-ID: <874prhvyp8.fsf@trews52.bothi.fi>

Greetings,

I tried to git-cvsimport an existing project but there seemed to be
something wrong with the result.  On closer inspection I noticed
that contents of files that had never been modified in trunk
corresponded to revision 1.1 instead of the tip of the vendor
branch in the generated master and origin branches.

In other words (using zsh):

> mkdir test
> cd test
> mkdir repo
> export CVSROOT=`pwd`/repo
> cvs init
> mkdir foo
> cd foo
> echo lahna > kala.txt
> cvs import -m "Initial vendor import." foo vendor vendor-v1
> cd ..
> rm -r foo
> cvs co foo
> cd foo
> cvs up -rvendor
> echo hauki >! kala.txt
> cvs commit -m "Fake 2nd. vendor import."
> cvs up -A
> cat kala.txt
hauki
> cd ..
> git-cvsimport -d $CVSROOT -C foo.git foo
> cd foo.git
> git-checkout -f master
> cat kala.txt
lahna

I would have expected to get "hauki" from that last "cat kala.txt"
as well.  Is this a known problem or a feature?  In either case, how
should I work around it?

-- 
Hannu