From: Martin Langhoff <martin.langhoff@gmail.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Michael J Gruber <git@drmicha.warpmail.net>,
Junio C Hamano <gitster@pobox.com>,
Heiko Voigt <git-list@hvoigt.net>,
ydirson@altern.org, git@vger.kernel.org, CVSps@dm.cobite.com
Subject: Re: started a cvsps testsuite Was: Re: [PATCH v3 0/2] cvsimport: add test illustrating a bug in cvsps
Date: Mon, 23 Mar 2009 20:06:55 +0100 [thread overview]
Message-ID: <46a038f90903231206i9f1dde2pb12fab3764e55cbd@mail.gmail.com> (raw)
In-Reply-To: <20090323181110.GB26678@macbook.lan>
On Mon, Mar 23, 2009 at 7:11 PM, Heiko Voigt <hvoigt@hvoigt.net> wrote:
> I just started a very simple but hopefully effective testsuite to
> collect all the issues we found with cvsps.
Excellent effort. One thing I found when I was debugging (and trying
to understand) corner cases in cvs imports was the test suite for the
cvs2svn importer. It had a number of tiny cvs repositories that were
broken in various ways.
The test cvs repos, straight from the svn repo for cvs2svn are in
http://cvs2svn.tigris.org/svn/cvs2svn/trunk/test-data/ - access with
user:guest and an empty password.
...
> Hopefully we can collect some more specifics about the situations where
> cvsps fails and most importantly the amount of coding needed for fixing.
> From there on it should be easier to decide which route to follow for
> a robust inbuild git cvsimport.
Some cvs repos are ambiguous. Others are "impossible", fruits of
direct file manipulation. cvs2svn has a fairly robust (and
inordinately slow!) approach, but you cannot rerun it to get
incremental imports.
It is certainly possible... and bloody hard!
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2009-03-23 19:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 18:49 [PATCH] cvsimport: add test illustrating a bug in cvsps Heiko Voigt
2009-02-23 20:35 ` Heiko Voigt
2009-02-24 5:00 ` Michael Haggerty
2009-03-02 17:59 ` [PATCH v2 0/1] " Heiko Voigt
2009-03-02 17:59 ` [PATCH v2 1/1] " Heiko Voigt
2009-03-09 11:26 ` [CVSPS PATCH] fix: correct rev order in case commiters clocks were not syncronised Heiko Voigt
2009-03-09 15:02 ` Michael Haggerty
2009-03-18 17:33 ` [PATCH v3 0/2] cvsimport: add test illustrating a bug in cvsps Heiko Voigt
2009-03-18 18:22 ` Junio C Hamano
2009-03-19 10:41 ` Michael J Gruber
2009-03-19 11:00 ` Johannes Schindelin
2009-03-19 11:22 ` Michael J Gruber
2009-03-21 5:41 ` Michael Haggerty
2009-03-23 18:11 ` started a cvsps testsuite Was: " Heiko Voigt
2009-03-23 19:06 ` Martin Langhoff [this message]
2009-03-24 4:50 ` Michael Haggerty
2009-04-06 19:01 ` Heiko Voigt
2009-03-23 17:47 ` Heiko Voigt
2009-03-18 17:33 ` [PATCH v3 1/2] " Heiko Voigt
2009-03-18 17:33 ` [PATCH v3 2/2] cvsimport: extend testcase about patchset order to contain branches Heiko Voigt
2009-03-18 17:34 ` [CVSPS PATCH v2] fix: correct rev order in case commiters clocks were not syncronised Heiko Voigt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46a038f90903231206i9f1dde2pb12fab3764e55cbd@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=CVSps@dm.cobite.com \
--cc=git-list@hvoigt.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=mhagger@alum.mit.edu \
--cc=ydirson@altern.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).