threads / discuss / 32594

parsecvs has been salvaged

Subject: parsecvs has been salvaged

## tl;dr

3 messages between Jan 11, 2013 and Jan 11, 2013.

replies: 2people: 2as markdown or json

Eric S. Raymond· Jan 11, 2013, 11:21 UTC · lore

Since Heiko Voigt and others were concerned about this, I report that I have successfully salvaged the parsecvs code. I now have it emitting a correct-looking fast-import stream for my main test repository.

I'm not ready to ship it yet because there are several features I think it ought to have before I do. An -R option like cvsps's; correct interpretation of a third timezone field as in cvsps; and, most significantly, I want to make sure it emits warnings for important error and problem conditions like unresolvable tags and absence of commitids.

But these are all relatively minor issues. It is likely I will be able to ship early next week, at which point I will add support for parsecvs as a third engine in new cvsimport.

This next step in the larger program will be factoring out the cvsps test suite and applying it to all three of cvsps, cvs2git, and parsecvs so I can compare results.

-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Americans have the right and advantage of being armed - unlike the citizens
of other countries whose governments are afraid to trust the people with arms.
	-- James Madison, The Federalist Papers
Bart Massey· Jan 11, 2013, 18:25 UTC · re: Eric S. Raymond · lore

Re: parsecvs has been salvaged

Very cool! I'm glad you got it doing what you wanted; I'll be interested to see how parsecvs compares in quality and performance to cvs2git and cvsps. --Bart

On Fri, Jan 11, 2013 at 3:21 AM, Eric S. Raymond <esr@thyrsus.com> wrote:
Show 24 quoted lines
> Since Heiko Voigt and others were concerned about this, I report that
> I have successfully salvaged the parsecvs code. I now have it emitting
> a correct-looking fast-import stream for my main test repository.
>
> I'm not ready to ship it yet because there are several features I
> think it ought to have before I do.  An -R option like cvsps's;
> correct interpretation of a third timezone field as in cvsps; and,
> most significantly, I want to make sure it emits warnings for important
> error and problem conditions like unresolvable tags and absence of
> commitids.
>
> But these are all relatively minor issues. It is likely I will be able
> to ship early next week, at which point I will add support for
> parsecvs as a third engine in new cvsimport.
>
> This next step in the larger program will be factoring out the cvsps
> test suite and applying it to all three of cvsps, cvs2git, and
> parsecvs so I can compare results.
> --
>                 <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>
> Americans have the right and advantage of being armed - unlike the citizens
> of other countries whose governments are afraid to trust the people with arms.
>         -- James Madison, The Federalist Papers
Eric S. Raymond· Jan 11, 2013, 19:02 UTC · re: Bart Massey · lore

Re: parsecvs has been salvaged

Bart Massey <bart@cs.pdx.edu>:
> Very cool! I'm glad you got it doing what you wanted; I'll be
> interested to see how parsecvs compares in quality and performance to
> cvs2git and cvsps. --Bart

And now it has that -R option and correctly interprets the timezone field. (I've been busy this morning.) I'm working on the no-commitids warning now.

Oh, and it now has...actual documentation, too. :-)
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

← back to recent threads