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

Re: Using subversion tools on Mozilla CVS

From
Sean <seanlkml@sympatico.ca>
Date
Jun 4, 2006, 15:20 UTC
Message-ID
<BAYC1-PASMTP08068F9BD23CF4FA8A1BDBAE970@CEZ.ICE>
In-Reply-To
<9e4733910606032009p252ff5fai7401401427ae3ec3@mail.gmail.com>

On Sat, 3 Jun 2006 23:09:00 -0400 "Jon Smirl" <jonsmirl@gmail.com> wrote:

Show 8 quoted lines
> I found this tool written in Python for importing CVS into Subversion.
> It seems to be handling the Mozilla CVS repository with fewer problems
> than parsecvs.
> 
> http://cvs2svn.tigris.org/cvs2svn.html
> 
> Since I'm not a native Python speaker, anyone else want to give a try
> at changing it to support git?
 
Hi Jon,

If you haven't tried to import into git with a recent version of git-cvsimport, it would be worth a shot.

As for the tool you've referenced above, it does look pretty good. It makes multiple passes and saves to a temp file after each, letting you resume from that point and means it can use less memory overall.

It can produce a pretty straight forward looking dump file if you pass it the "--dump-only" option, rather than it pushing the results into svn; for instance:

 $ cvs2svn --dump-only --dumpfile DUMPFILE <cvs directory>

It shouldn't be too hard to write a script that imports the revisions found in the resulting DUMPFILE into git.

Sean
Previous: Jon SmirlNext: Jon Smirl
Message 2 of 3 in “Using subversion tools on Mozilla CVS”
  1. Jon SmirlJun 4, 2006
  2. SeanJun 4, 2006
  3. Jon SmirlJun 4, 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.