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

Importing from CVS issues

From
ABAlex Bennee <kernel-hacker@bennee.com>
Date
Aug 16, 2005, 10:41 UTC
Message-ID
<1124188894.7444.9.camel@okra.transitives.com>
Hi,

We've been having issues with CVS for some time and I thought I'd give git a spin. To do some like-for-like tests I'm having a go at importing our cvs repository into git so I can do some benchmarks on things like branch creation as well as play around with the visualisation tools.

Obviously the CVS repo is non-trivial as we have many branches (one per change developed). I've been trying to import script but it seems to falling over. For starters cvsps is spitting out lots of messages along the lines of:

WARNING: revision 1.3.2.1 of file scripts/xmltools/t/runtests.pl on
unnamed branch
Before the import script finally dies with:
WARNING: revision 1.3.2.1 of file
scripts/xmltools/t/data/gzip/DO-NOT-BACKUP on unnamed branch
DONE; creating master branch
cp: cannot stat `/export/test/cvstogit/.git/refs/heads/origin': No such
file or directory
usage: git-read-tree (<sha> | -m [-u] <sha1> [<sha2> [<sha3>]])

Is this a just a case of the cvsps not giving output the script can deal with? Any suggestions on how I can proceed with diagnosing what went wrong?

-- Alex, homepage: http://www.bennee.com/~alex/ Barometer, n.: An ingenious instrument which indicates what kind of weather we are having. -- Ambrose Bierce, "The Devil's Dictionary"

Next: Martin Langhoff
Message 1 of 5 in “Importing from CVS issues”
  1. Alex BenneeAug 16, 2005
  2. Martin LanghoffAug 16, 2005
  3. Alex BenneeAug 16, 2005
  4. David KågedalAug 16, 2005
  5. Alex BenneeAug 16, 2005

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.