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

Challenge: Importing Mozilla CVS into git

From
Jon Smirl <jonsmirl@gmail.com>
Date
Jul 26, 2006, 21:08 UTC
Message-ID
<9e4733910607261408m6f3980fbxc1793ca432ef3b0a@mail.gmail.com>

If anyone is looking for a project, it is still not possible to import Mozilla CVS into git and then do increment updates. As I recall from the last time I played with it, cvsps throws away some of the branches because it thinks they are in a loop. parsecvs is unable to complete the entire import without getting errors and aborting.

cvs2svn can import the entire Mozilla repository correctly. But it imports it to svn and does not have incremental support.

Best solution would be to use the parser from parsecvs, apply the change set detection algorithm from cvs2svn, and then add cvsps' incremental update.

It's also not reasonable to fork git processes, there are about a million change sets in Mozilla and it takes days of CPU time to do 1M forks. The import app needs to use a library version of git. Another tactic to reduce CPU time is to directly write pack files with the delta in a first pass, and add the change set index in a later pass.

-- 
Jon Smirl
jonsmirl@gmail.com
Message 1 of 1 in “Challenge: Importing Mozilla CVS into git”
  1. Jon SmirlJul 26, 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.