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

Re: [PATCH] Remove the suggestion to use parsecvs, which is currently broken.

From
Eric S. Raymond <esr@thyrsus.com>
Date
Jan 7, 2013, 20:41 UTC
Message-ID
<20130107204132.GA23867@thyrsus.com>
In-Reply-To
<7vehhwiyt6.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com>:
> In the longer term, if parsecvs is revived either by Eric or
> somebody else, we will add the mention back to the documentation,
> probably with an updated URL.

I'm working on the revival right now. Repository generation is still broken, and likely to remain so until I can make the export-stream stage work, but just a few minutes ago I coaxed it into generating what looks like graphviz markup describing a commit graph on standard output.

Even though dot(1) barfs on the markup, this is encouraging. It almost certainly means that the analysis and parsing stages aren't broken, and by stubbing out enough functions I can figure out what is being passed to the broken repository-maker well enough for my purposes.

Actually, I've already figured out how to generate blob and commit-header markup. The hard part is generating fileops; I don't quite understand the generated data structures well enough to do that yet. But I'm making progress, and feeling more optimistic than I was yesterday.

In related news, I've sent Michael Haggerty patches that fix the visible problems with cvs2git that I enumerated in previous mail.

-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Previous: Junio C HamanoNext: Chris Packham
Message 8 of 9 in “Remove the suggestion to use parsecvs, which is currently broken.”
  1. Remove the suggestion to use parsecvs, which is currently broken.Eric S. Raymond, Dec 28, 2012
  2. Junio C HamanoDec 28, 2012
  3. Heiko VoigtDec 28, 2012
  4. Eric S. RaymondDec 29, 2012
  5. Heiko VoigtJan 6, 2013
  6. Eric S. RaymondJan 6, 2013
  7. Junio C HamanoJan 7, 2013
  8. Eric S. RaymondJan 7, 2013
  9. Chris PackhamJan 1, 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.