All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gerd v. Egidy" <lists@egidy.de>
To: mlmmj@mlmmj.org
Subject: public code repository (was Re: [PATCH] add MIME-aware footers)
Date: Fri, 19 Feb 2010 08:40:21 +0000	[thread overview]
Message-ID: <201002190940.21471.lists@egidy.de> (raw)

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



                 reply	other threads:[~2010-02-19  8:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201002190940.21471.lists@egidy.de \
    --to=lists@egidy.de \
    --cc=mlmmj@mlmmj.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.