git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: Change in cvsps maintainership, abd a --fast-export option
Date: Fri, 21 Dec 2012 05:44:37 -0500	[thread overview]
Message-ID: <20121221104437.GA5244@thyrsus.com> (raw)
In-Reply-To: <50D4199C.6000002@alum.mit.edu>

Michael Haggerty <mhagger@alum.mit.edu>:
> In 2009 I added tests demonstrating some of the erroneous behavior of
> git-cvsimport.  The failing tests in t9601-t9603 are concrete examples
> of the problems mentioned in the manpage.

Thanks, that will be extremely useful. One of the things I'm putting effort
into is building a good test suite for the tool; I may well be able to adapt
your tests directly.
>
> If you haven't yet seen it, there is a writeup of the algorithm used by
> cvs2git to infer the history of a CVS repository [1].  If your goal is
> to make cvsps more robust, you might want to consider the ideas
> described there.

I shall do so.  Their design ideas may well be interesting, even though I
don't trust their code.  I've seem cvs2svn drop far too many weird artifacts 
and just plain broken commits in the back history of Subversion repositories.
I don't know if this is due to design problems, implementation bugs, or both.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

  reply	other threads:[~2012-12-21 10:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 21:56 Change in cvsps maintainership, abd a --fast-export option Eric S. Raymond
2012-12-21  8:11 ` Michael Haggerty
2012-12-21 10:44   ` Eric S. Raymond [this message]
2012-12-21 19:19     ` Michael Haggerty
2012-12-21 21:43       ` Eric S. Raymond
2012-12-21 22:16         ` Michael Haggerty
2012-12-22  3:47     ` Heiko Voigt
2012-12-22  6:21       ` Eric S. Raymond
2012-12-22 13:04         ` Heiko Voigt
2012-12-22 14:15           ` Eric S. Raymond
2012-12-23 19:57             ` Heiko Voigt
2012-12-22 14:04       ` Eric S. Raymond
2012-12-22 14:10         ` Antoine Pelisse
2012-12-22 14:17           ` Eric S. Raymond
2012-12-22 16:25           ` Andreas Schwab
2012-12-22 14:21         ` Andreas Schwab

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=20121221104437.GA5244@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    /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).