{"thread":{"id":"6129","subject":"git-cvsimport doesn't support the default branch mechanism?","startedAt":"2006-12-27T21:03:15Z","lastAt":"2006-12-27T21:03:15Z","messageCount":1,"participants":["Hannu Koivisto"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"30361","messageId":"874prhvyp8.fsf@trews52.bothi.fi","threadId":"6129","inReplyTo":null,"subject":"git-cvsimport doesn't support the default branch mechanism?","fromName":"Hannu Koivisto","fromEmail":"azure@iki.fi","sentAt":"2006-12-27T21:03:15Z","receivedAt":"2006-12-27T21:03:15Z","isPatch":false,"sender":{"key":"azure@iki.fi","avatar":null},"body":"Greetings,\n\nI tried to git-cvsimport an existing project but there seemed to be\nsomething wrong with the result.  On closer inspection I noticed\nthat contents of files that had never been modified in trunk\ncorresponded to revision 1.1 instead of the tip of the vendor\nbranch in the generated master and origin branches.\n\nIn other words (using zsh):\n\n> mkdir test\n> cd test\n> mkdir repo\n> export CVSROOT=`pwd`/repo\n> cvs init\n> mkdir foo\n> cd foo\n> echo lahna > kala.txt\n> cvs import -m \"Initial vendor import.\" foo vendor vendor-v1\n> cd ..\n> rm -r foo\n> cvs co foo\n> cd foo\n> cvs up -rvendor\n> echo hauki >! kala.txt\n> cvs commit -m \"Fake 2nd. vendor import.\"\n> cvs up -A\n> cat kala.txt\nhauki\n> cd ..\n> git-cvsimport -d $CVSROOT -C foo.git foo\n> cd foo.git\n> git-checkout -f master\n> cat kala.txt\nlahna\n\nI would have expected to get \"hauki\" from that last \"cat kala.txt\"\nas well.  Is this a known problem or a feature?  In either case, how\nshould I work around it?\n\n-- \nHannu\n"}]}