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

Re: Fixes to parsecvs

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 6, 2006, 15:26 UTC
Message-ID
<Pine.LNX.4.63.0604061723410.23681@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<1144334896.2303.259.camel@neko.keithp.com>
Hi,
On Thu, 6 Apr 2006, Keith Packard wrote:
Show 7 quoted lines
> On Thu, 2006-04-06 at 14:08 +0200, Jan-Benedict Glaw wrote:
> 
> > But it seems it now starts to really consume memory:
> 
> The question is whether it needs to be more efficient so that people can 
> constantly convert repositories or whether moving the repository to a 
> sufficiently large machine for the one-time conversion is 'good enough'.

Keep in mind that there are many more valid uses for tracking a CVS repository than to import it once.

Ciao, Dscho

Previous: Keith PackardNext: Jan-Benedict Glaw
Message 4 of 13 in “Fixes to parsecvs”
  1. Keith PackardApr 6, 2006
  2. Jan-Benedict GlawApr 6, 2006
  3. Keith PackardApr 6, 2006
  4. Johannes SchindelinApr 6, 2006
  5. Jan-Benedict GlawApr 6, 2006
  6. Keith PackardApr 6, 2006
  7. Francois RomieuApr 9, 2006
  8. Jim RadfordApr 6, 2006
  9. Keith PackardApr 6, 2006
  10. Martin LanghoffApr 6, 2006
  11. Keith PackardApr 6, 2006
  12. Martin LanghoffApr 6, 2006
  13. Keith PackardApr 7, 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.