[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mlmmj
Subject:    public code repository (was Re: [PATCH] add MIME-aware footers)
From:       "Gerd v. Egidy" <lists () egidy ! de>
Date:       2010-02-19 8:40:21
Message-ID: 201002190940.21471.lists () egidy ! de
[Download RAW message or body]

On Thursday 18 February 2010 18:54:43 Mads Martin Jørgensen wrote:
> On 18/02/2010, at 18.22, Morten Shearman Kirkegaard wrote:
> >> BTW, is the CVS available to the public somewhere?
> >
> > Not at the moment, but if you drop Mads Martin a mail, you might be able
> > to convince him to create an account for you.
> 
> I would much rather someone converted it to something and put it somewhere
>  :)

I would much rather decide what something should be before starting to convert 
;)

I'd vote for git and I can offer to convert the history from cvs to git. But 
I'm just occasionally sending a patch so my preferences should not count so 
much. Mostly the maintainer should be comfortable with the "something" chosen.

I've made good experience with git. But when deciding where to host it, you 
should check if you can give commit rights to others and how hard it is to do 
so.

I'm hosting some projects on our own server: 
http://developer.intra2net.com/git/

But it took a while to set it up so that others can commit, but just to the 
specific projects they are allowed to.

I'm also working with a project hosted on github.com. It's very easy to give 
rights to others. It's even more easy to merge some specific patches someone 
else has done. So I'd recommend to use github.

Kind regards,

Gerd

-- 
Address (better: trap) for people I really don't want to get mail from:
jonas@cactusamerica.com



[prev in list] [next in list] [prev in thread] [next in thread]