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

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

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 5, 2013, 22:57 UTC
Message-ID
<20130105225740.GC3247@elie.Belkin>
In-Reply-To
<20130105151106.GA1938@thyrsus.com>
Eric S. Raymond wrote:
Show 5 quoted lines
> Michael Haggerty wants me to trust that cvs2git's analysis stage has
> been fixed, but I must say that is a more difficult leap of faith when
> two of the most visible things about it are still (a) a conspicuous
> instance of interface misdesign, and (b) documentation that is careless and
> incomplete.

For what it's worth, I use cvs2git quite often. I've found it to work well and its code to be clear and its developers responsive. But I don't mind if we disagree, and multiple implementations to explore the design space of importers doesn't seem like a terrible outcome.

Thanks for your work, Jonathan

Previous: Eric S. RaymondNext: Michael Haggerty
Message 8 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.