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

[PATCH v3 0/5] Add more tests of cvsimport

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Feb 23, 2009, 05:08 UTC
Message-ID
<1235365694-28935-1-git-send-email-mhagger@alum.mit.edu>
In-Reply-To
<7vzlge1kob.fsf@gitster.siamese.dyndns.org>

@Junio, sorry for the screwup. The attached patch series definitely works on my machine (Linux, cvsps 2.1).

Junio C Hamano wrote:
> Thanks, both.  I generally am not very fond of adding tests without
> intention to look into fixes, but if they make outstanding bugs more
> visible, they may have the effect of shaming the original authors
> badly enough to step in in the effort of fixing them :-)

Please note that the new tests only check the very basic minimal functionality of a conversion tool: that all of the CVS branches are present, and that the tips of the branches have the same content as those in the original CVS repository. So far they cover perhaps 5% of the cvs2svn/cvs2git test repository.

I am convinced that robust cvsps-based repository conversion is so fundamentally impossible [1] that I am not interested in working on it. If people absolutely need incremental conversions, then let them struggle on. But let them be warned :-)

Cheers, Michael

[1] http://selenic.com/pipermail/mercurial-devel/2008-February/004975.html
Previous: Junio C HamanoNext: Michael Haggerty
Message 8 of 14 in “Add more tests of cvsimport”
  1. 0/4 Add more tests of cvsimportMichael Haggerty, Feb 21, 2009
  2. 1/5 Start a library for cvsimport-related testsMichael Haggerty, Feb 21, 2009
  3. 2/5 Use CVS's -f option if available (ignore user's ~/.cvsrc file)Michael Haggerty, Feb 21, 2009
  4. 3/5 Test contents of entire cvsimported "master" tree contentsMichael Haggerty, Feb 21, 2009
  5. 4/5 Add some tests of git-cvsimport's handling of vendor branchesMichael Haggerty, Feb 21, 2009
  6. 5/5 Add a test of "git cvsimport"'s handling of tags and branchesMichael Haggerty, Feb 21, 2009
  7. Junio C HamanoFeb 22, 2009
  8. 0/5 Add more tests of cvsimportMichael Haggerty, Feb 23, 2009
  9. 1/5 Start a library for cvsimport-related testsMichael Haggerty, Feb 23, 2009
  10. 2/5 Use CVS's -f option if available (ignore user's ~/.cvsrc file)Michael Haggerty, Feb 23, 2009
  11. 3/5 Test contents of entire cvsimported "master" tree contentsMichael Haggerty, Feb 23, 2009
  12. 4/5 Add some tests of git-cvsimport's handling of vendor branchesMichael Haggerty, Feb 23, 2009
  13. 5/5 Add a test of "git cvsimport"'s handling of tags and branchesMichael Haggerty, Feb 23, 2009
  14. Junio C HamanoFeb 22, 2009

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.