git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-cvsimport doesn't support the default branch mechanism?

From
HKHannu Koivisto <azure@iki.fi>
Date
Dec 27, 2006, 21:03 UTC
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):
Show 18 quoted lines
> 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
Show 5 quoted lines
> 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
Message 1 of 1 in “git-cvsimport doesn't support the default branch mechanism?”
  1. Hannu KoivistoDec 27, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.