On 5/16/06, David Lang <dlang@digitalinsight.com> wrote:
quoted text
> 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).

quoted text
> 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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html