From: Michael Haggerty <mhagger@alum.mit.edu>
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net, Johannes.Schindelin@gmx.de,
jnareb@gmail.com, Michael Haggerty <mhagger@alum.mit.edu>
Subject: [PATCH v3 0/5] Add more tests of cvsimport
Date: Mon, 23 Feb 2009 06:08:09 +0100 [thread overview]
Message-ID: <1235365694-28935-1-git-send-email-mhagger@alum.mit.edu> (raw)
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
next prev parent reply other threads:[~2009-02-23 5:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 13:04 [PATCH v2 0/4] Add more tests of cvsimport Michael Haggerty
2009-02-21 13:04 ` [PATCH v2 1/5] Start a library for cvsimport-related tests Michael Haggerty
2009-02-21 13:04 ` [PATCH v2 2/5] Use CVS's -f option if available (ignore user's ~/.cvsrc file) Michael Haggerty
2009-02-21 13:04 ` [PATCH v2 3/5] Test contents of entire cvsimported "master" tree contents Michael Haggerty
2009-02-21 13:04 ` [PATCH v2 4/5] Add some tests of git-cvsimport's handling of vendor branches Michael Haggerty
2009-02-21 13:04 ` [PATCH v2 5/5] Add a test of "git cvsimport"'s handling of tags and branches Michael Haggerty
2009-02-22 16:49 ` [PATCH v2 4/5] Add some tests of git-cvsimport's handling of vendor branches Junio C Hamano
2009-02-23 5:08 ` Michael Haggerty [this message]
2009-02-23 5:08 ` [PATCH v3 1/5] Start a library for cvsimport-related tests Michael Haggerty
2009-02-23 5:08 ` [PATCH v3 2/5] Use CVS's -f option if available (ignore user's ~/.cvsrc file) Michael Haggerty
2009-02-23 5:08 ` [PATCH v3 3/5] Test contents of entire cvsimported "master" tree contents Michael Haggerty
2009-02-23 5:08 ` [PATCH v3 4/5] Add some tests of git-cvsimport's handling of vendor branches Michael Haggerty
2009-02-23 5:08 ` [PATCH v3 5/5] Add a test of "git cvsimport"'s handling of tags and branches Michael Haggerty
2009-02-22 16:48 ` [PATCH v2 0/4] Add more tests of cvsimport Junio C Hamano
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=1235365694-28935-1-git-send-email-mhagger@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
/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).