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

Re: Any tricks for speeding up cvsps?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 8, 2008, 12:23 UTC
Message-ID
<alpine.LSU.1.00.0802081222400.11591@racer.site>
In-Reply-To
<47AC1FDC.9000502@glidos.net>
Hi,
On Fri, 8 Feb 2008, Paul Gardiner wrote:
Show 6 quoted lines
> I'm trying to convert a huge cvs repository. I've left cvsps running for 
> days. First attempt, stderr filled my disc with warnings about tags that 
> couldn't be associated with any one commit, without producing anything 
> from stdout. I'm now redirecting stderr to /dev/null, but it still just 
> sits there producing nothing.  Is git-cvsimport infeasible for large 
> repositories, or are there tricks I might use?

The obvious thing is to have the CVS repository locally. And then on a ramdisk.

Hth, Dscho

Previous: Paul GardinerNext: Jakub Narebski
Message 8 of 9 in “Any tricks for speeding up cvsps?”
  1. Paul GardinerFeb 8, 2008
  2. Karl HasselströmFeb 8, 2008
  3. Michael HaggertyFeb 8, 2008
  4. Johannes SixtFeb 8, 2008
  5. Paul GardinerFeb 8, 2008
  6. Johannes SixtFeb 8, 2008
  7. Paul GardinerFeb 9, 2008
  8. Johannes SchindelinFeb 8, 2008
  9. Jakub NarebskiFeb 8, 2008

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.