From: Heiko Voigt <hvoigt@hvoigt.net>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: Yann Dirson <ydirson@free.fr>,
Michael Haggerty <mhagger@alum.mit.edu>,
Antoine Pelisse <apelisse@gmail.com>,
Bart Massey <bart@cs.pdx.edu>, Keith Packard <keithp@keithp.com>,
David Mansfield <david@cobite.com>,
git@vger.kernel.org
Subject: Re: cvsps, parsecvs, svn2git and the CVS exporter mess
Date: Sun, 23 Dec 2012 21:21:11 +0100 [thread overview]
Message-ID: <20121223202111.GB29354@book-mint> (raw)
In-Reply-To: <20121222173649.04C5B44119@snark.thyrsus.com>
Hi,
On Sat, Dec 22, 2012 at 12:36:48PM -0500, Eric S. Raymond wrote:
> If we can agree on this, I'll start a public repo, and contribute my
> Python framework - it's more capable than any of the shell harnesses
> out there because it can easily drive interleaved operations on multiple
> checkout directories.
Please share so we can have a look. BTW, where can I find your cvsps
code?
> Anybody who is still interested in this problem should contribute
> tests. Heiko Voigt, I'd particularly like you in on this.
If it does not take to much effort I could port my tests to the new
framework. Since I currently are not in active need of cvs conversions
its not of big interest to me anymore. But if it does not take too much
time I am happy to help.
>From my past cvs conversion experiences my personal guess is that
cvs2svn will win this competition.
Cheers Heiko
next prev parent reply other threads:[~2012-12-23 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 17:36 cvsps, parsecvs, svn2git and the CVS exporter mess Eric S. Raymond
2012-12-23 20:21 ` Heiko Voigt [this message]
2012-12-23 22:45 ` Eric S. Raymond
2013-01-03 15:37 ` Michael Haggerty
2013-01-03 20:53 ` Eric S. Raymond
2013-01-05 8:27 ` Max Horn
2013-01-05 15:11 ` Eric S. Raymond
2013-01-05 22:57 ` Jonathan Nieder
2013-01-06 11:15 ` Michael Haggerty
[not found] ` <CAA6gtpky9JxFDdpLM6kY9su-9FWX8RoWHU4uptd_Zk+ZJuhrtA@mail.gmail.com>
2013-01-05 15:58 ` Eric S. Raymond
2013-01-03 15:51 ` Martin Langhoff
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=20121223202111.GB29354@book-mint \
--to=hvoigt@hvoigt.net \
--cc=apelisse@gmail.com \
--cc=bart@cs.pdx.edu \
--cc=david@cobite.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=keithp@keithp.com \
--cc=mhagger@alum.mit.edu \
--cc=ydirson@free.fr \
/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).