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

cvs2svn and git progress

From
Jon Smirl <jonsmirl@gmail.com>
Date
Aug 10, 2006, 01:29 UTC
Message-ID
<9e4733910608091828l1744822cjf001b2722fea6c5a@mail.gmail.com>

I've finally got cvs2svn running through pass 7 now. It took me a while to fix errors where it would run five hours and then die with "key error 357" or something similar.

pass 1: 7663 seconds pass 2: 1 second pass 3: 1043 seconds pass 4: 3 seconds pass 5: 204 seconds pass 6: 1165 seconds pass 7: 37 seconds

Total is a little less than three hours. The new cvs2svn code is many times faster than the old version which ran for several days. The total includes the time needed to write the git pack and index file for the revisions.

Pass 8 is where the final output is generated. Now that I have a database I can only run pass 8 as needed to work on the back-end code.

I believe I have the sha1 from the git revisions correctly in the final database but I need to write my first try at dumping the change sets to be sure.

-- 
Jon Smirl
jonsmirl@gmail.com
Next: Martin Langhoff
Message 1 of 4 in “cvs2svn and git progress”
  1. Jon SmirlAug 10, 2006
  2. Martin LanghoffAug 10, 2006
  3. Jon SmirlAug 10, 2006
  4. Jakub NarebskiAug 10, 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.