Re: Turning cvs2{svn,git} into cvs2hg

Greg Ward <[email protected]>
Newsgroups gmane.comp.version-control.subversion.cvs2svn.devel
Message-ID <cd4419280907311537q2544bbccpb02571a218701201__32877.3026391447$1249116490$gmane$org@mail.gmail.com>
On Fri, Jul 31, 2009 at 6:16 PM, Michael Haggerty<[email protected]> wrote:
> You are quite right that cvs2git has a burning need for such a
> verification tool.  I built some (very!) minimal tools verifying CVS ->
> git conversions and contributed them to the git project for their tests
> of git-cvsimport.  It can be found in the git "next" branch under
> t/lib-cvs.sh and t/t96*.
>
> It would be great to have a generic basic "sine qua non" verifier that
> could be applied to any of the outputs.

Hang on a sec... are you telling me that even *you* didn't know about
contrib/verify-cvs2svn.py?
Then I don't feel so bad for asking "where is it?" and then finding it
5 minutes after asking.  ;-)
Anyways, I've started hacking on it.  My patches so far are:

  http://vc.gerg.ca/hg/cvs2svn/rev/e79fb91e68e6
  http://vc.gerg.ca/hg/cvs2svn/rev/0ba887e6e58e
  http://vc.gerg.ca/hg/cvs2svn/rev/5991b868c571
  http://vc.gerg.ca/hg/cvs2svn/rev/d79a9c0c045e
  http://vc.gerg.ca/hg/cvs2svn/rev/018436f39d73

The last patch adds Mercurial support.  Should be relatively
straightforward to add git support too, as long as 'git tags' and 'git
branches' are as easy to parse as 'hg {tags,branches} -q' and 'svn
ls'.

Or, if you just want to see the current code:

  http://vc.gerg.ca/hg/cvs2svn/file/018436f39d73/contrib/verify-cvs2svn.py

BTW, please let me know if you love my patches and want to immediately
start applying them.
Or if you hate, hate, hate them and will never let them near your
official repo.  If you're in the middle,
that's just fine... gives me time to polish things a bit more.  ;-)

Will respond to your other stuff later.

Greg

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2377617

To unsubscribe from this discussion, e-mail: [[email protected]].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.