git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Change in cvsps maintainership, abd a --fast-export option

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Dec 21, 2012, 22:16 UTC
Message-ID
<50D4DFBD.7080708@alum.mit.edu>
In-Reply-To
<20121221214311.GA29147@thyrsus.com>
On 12/21/2012 10:43 PM, Eric S. Raymond wrote:
Show 5 quoted lines
> Michael Haggerty <mhagger@alum.mit.edu>:
>> Perhaps your experience is with an older version of cvs2svn? 
> 
> Well, it has been at least four years since I ran it on anything.
> Maybe that counts as old.

cvs2svn version 2.0 (Aug 2007) totally changed how cvs2svn deduces changesets. Any results from before that are utterly irrelevant to modern times.

The changes between version 2.0 and version 2.4 (Sep 2012) have done a lot more to improve the quality of the conversion. The state of the art is far beyond what it was four years ago.

Show 15 quoted lines
>>                                                             If not,
>> please be specific rather than just making complaints that are too vague
>> to be rebutted or fixed (whichever is appropriate).  I put a *lot* of
>> effort into getting cvs2svn to run correctly, and I take bug reports
>> very seriously.
> 
> I can't be specific now, but that may change shortly.  I'm putting
> together a test suite for cvsps with the specific intention of
> capturing as many odd corner cases as I can.  (I just finished writing
> a small Python framework for expressing interleaved CVS command
> sequences on multiple checkouts in a way that can be easily run.)
> 
> It wouldn't be difficult for me to test whether these break cvs2svn. 
> You've established that someone over there is paying attention, so
> I'll do that, I guess.
I look forward to your results (whether positive or negative).
> I'm willing to share my test suite as well.  Do you have your own zoo
> of odd cases I could test on?
Yes, we have a rather extensive test suite that includes lots of CVS
perversions.  See run-tests.py and the CVS repositories under test-data.
 Unfortunately, the tests mostly cover only 2svn conversions, but since
most of the tricky work is in the common code that infers the CVS
history, cvs2git benefits from the tests too.

This discussion is getting pretty cvs2svn-specific, so we should probably move it over to the cvs2svn-dev mailing list.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Eric S. RaymondNext: Heiko Voigt
Message 6 of 16 in “Change in cvsps maintainership, abd a --fast-export option”
  1. Eric S. RaymondDec 20, 2012
  2. Michael HaggertyDec 21, 2012
  3. Eric S. RaymondDec 21, 2012
  4. Michael HaggertyDec 21, 2012
  5. Eric S. RaymondDec 21, 2012
  6. Michael HaggertyDec 21, 2012
  7. Heiko VoigtDec 22, 2012
  8. Eric S. RaymondDec 22, 2012
  9. Heiko VoigtDec 22, 2012
  10. Eric S. RaymondDec 22, 2012
  11. Heiko VoigtDec 23, 2012
  12. Eric S. RaymondDec 22, 2012
  13. Antoine PelisseDec 22, 2012
  14. Eric S. RaymondDec 22, 2012
  15. Andreas SchwabDec 22, 2012
  16. Andreas SchwabDec 22, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.