From: "Eric S. Raymond" <esr@thyrsus.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Heiko Voigt <hvoigt@hvoigt.net>, git@vger.kernel.org
Subject: Re: [PATCH] Remove the suggestion to use parsecvs, which is currently broken.
Date: Mon, 7 Jan 2013 15:41:33 -0500 [thread overview]
Message-ID: <20130107204132.GA23867@thyrsus.com> (raw)
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>
next prev parent reply other threads:[~2013-01-07 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 16:20 [PATCH] Remove the suggestion to use parsecvs, which is currently broken Eric S. Raymond
2012-12-28 19:28 ` Junio C Hamano
2012-12-28 23:01 ` Heiko Voigt
2012-12-29 4:42 ` Eric S. Raymond
2013-01-06 16:34 ` Heiko Voigt
2013-01-06 20:32 ` Eric S. Raymond
2013-01-07 19:21 ` Junio C Hamano
2013-01-07 20:41 ` Eric S. Raymond [this message]
2013-01-01 10:05 ` Chris Packham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130107204132.GA23867@thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).