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

Re: cvsps, parsecvs, svn2git and the CVS exporter mess

From
Eric S. Raymond <esr@thyrsus.com>
Date
Dec 23, 2012, 22:45 UTC
Message-ID
<20121223224542.GA16383@thyrsus.com>
In-Reply-To
<20121223202111.GB29354@book-mint>
Heiko Voigt <hvoigt@hvoigt.net>:
> Please share so we can have a look. BTW, where can I find your cvsps
> code?
https://gitorious.org/cvsps
Developments of the last 48 hours:
1. Andreas Schwab sent me a patch that uses commitids wherever the history
   has them - this makes all the time-skew problems go away.  I added code
   to warn if commitids aren't present, so users will get a clear indication
   of when time-skew problems might bite them versus when that is happily
   impossible.
2. I've scrapped a lot of obsolete code and options.  The repo head
   version uses what used to be called cvs-direct mode all the time
   now; it works, and the effect on performance is major.  This also
   means that cvsps doesn't need to use any local CVS commands or even
   have CVS installed where it runs.
> >From my past cvs conversion experiences my personal guess is that
> cvs2svn will win this competition.

That could be. But right now cvsps has one significant advantage over cvs2git (which parsecvs might share) - it's *blazingly* fast. So fast that I scrapped all the local-caching logic; there seems no point to it at today's network speeds, and that's one less layer of complications to go wrong.

I've removed a couple hundred lines of code and the program works better and faster than it did before. That's having a good day!

-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Previous: Heiko VoigtNext: Michael Haggerty
Message 3 of 11 in “cvsps, parsecvs, svn2git and the CVS exporter mess”
  1. Eric S. RaymondDec 22, 2012
  2. Heiko VoigtDec 23, 2012
  3. Eric S. RaymondDec 23, 2012
  4. Michael HaggertyJan 3, 2013
  5. Eric S. RaymondJan 3, 2013
  6. Max HornJan 5, 2013
  7. Eric S. RaymondJan 5, 2013
  8. Jonathan NiederJan 5, 2013
  9. Michael HaggertyJan 6, 2013
  10. Martin LanghoffJan 3, 2013
  11. Eric S. RaymondJan 5, 2013

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.