The Reposturgeon That Ate Sheboygan!
<p>Well-designed software suites should not only be correct, they should be able to demonstrate their own correctness.  This is why the new 2.10 release of reposurgeon features a new tool called &#8216;repodiffer&#8217;.  And yes, that is what it sounds like &#8211; a diff tool that operates not on files but entire repository histories.  You get a report on which revisions are identical, which are different, and in the latter case where the differences are, down to which files don&#8217;t match.  Commits to be paired are matched by committer and commit date.  Like reposurgeon, it will work on any version-control system that can emit a fast-import stream.</p>
<p><span id="more-4735"></span></p>
<p>If you tried running repodiffer on two repositories for different projects the output would be noise and coincidences.  What it&#8217;s really useful for is comparing two different attempts to lift a repository.  Don&#8217;t trust reposurgeon? Fine &#8211; lift your repo twice, once with git-svn or whatever tool strikes your fancy, then run repodiffer to see the differences.  <em>All</em> the differences, not just those in the master tip state. I&#8217;ve already found one bug in git-svn this way.</p>
<p>There are few other new goodies, like automatic translation of .cvsignore to .gitignore files (trivial, really &#8211; the syntax is upward-compatible).  Also, translations from Subversion now emulate Subversion&#8217;s default ignore-pattern behavior.</p>
<p>Also note the new web page comparing reposurgeon to other translation tools. To be extended&#8230; </p>
<p><a href="http://www.catb.org/esr/reposurgeon/">Fear the reposturgeon!</a></p>
