Re: gateway status?

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: May 16, 2006, 13:09 UTC
Message-ID: <46a038f90605160609u19a356ccx9467c32100731b9@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.62.0605151122500.29452@qynat.qvtvafvgr.pbz>

On 5/16/06, David Lang <dlang@digitalinsight.com> wrote:

> I seem to remember seeing discussion of gateways to cvs/svn that would let
> a project use a git repository and allow clients to use cvs/svn clients to
> retreive data.

David,

I suspect you might be thinking of git-cvsserver. The code has no known bugs, but is has only seen limited use by in-house dev teams.

A good measure is to run an import of the current cvs project (I would try both git-cvsimport and parsecvs) and then get a checkout via git-cvsserver.

Works great with traditional cvs cli and well behaved clients (TortoiseCVS).

Show 5 quoted lines

> am I remembering correctly, and are these tools ready for production use?
> the popfile project is getting ready to abandon sourceforge and move to
> self-hosting, but before I suggest that they use git I need to know the
> current status of these projects (I think the ability to export directly
> into the other interfaces is a significant advantage)

Moodle (a project I hack on) is in a similar situation, specially after the SF.net debacle with CVS. It is very likely that it will move to git with git-cvsserver providing "anon cvs" and cvs over ssh to a very limited set of people with commit rights but no development knowledge (translators, etc). So there is a path forward.

cheers,

martin