From: Anil Madhavapeddy <anil@recoil.org>
To: "François Bobot" <francois.bobot@cea.fr>
Cc: Simon Cruanes <simon.cruanes.2007@m4x.org>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list
Date: Tue, 14 Jan 2014 15:11:05 +0000 [thread overview]
Message-ID: <02078ABC-03C2-44C8-99FA-D7FA7E492BA7@recoil.org> (raw)
In-Reply-To: <52D55344.90109@cea.fr>
On 14 Jan 2014, at 15:09, François Bobot <francois.bobot@cea.fr> wrote:
>> Same, but I don't know gitlab so
>
> Just for information
>
> http://gitlab.org/
>
> GitLab is an open source private github. Just less mature and feature-full than github but it is open source, very alive and on your server. Very useful for developer teams which can't use a public github.
I installed an experimental read-only version of GitLab at:
http://git.ocaml.org/ocaml-compiler/ocaml/tree/trunk
I'm not in favour of maintaining it on an ongoing basis though. It's a bit of a Ruby hydra to keep updated and secure...
-anil
next prev parent reply other threads:[~2014-01-14 15:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 15:23 Adrien Nader
2014-01-11 15:41 ` Simon Cruanes
2014-01-13 9:04 ` Adrien Nader
2014-01-13 9:51 ` François Bobot
2014-01-13 10:27 ` Gabriel Scherer
2014-01-13 11:14 ` Daniel Bünzli
2014-01-13 13:26 ` Gabriel Scherer
2014-01-13 13:43 ` Thomas Refis
2014-01-13 13:51 ` Gabriel Scherer
2014-01-13 13:57 ` Simon Cruanes
2014-01-13 15:03 ` Török Edwin
2014-01-13 13:58 ` Kakadu
2014-02-17 22:55 ` Richard W.M. Jones
2014-01-13 13:57 ` Daniel Bünzli
2014-01-13 22:30 ` Adrien Nader
2014-01-13 22:39 ` Simon Cruanes
2014-01-13 23:09 ` Adrien Nader
2014-01-14 11:13 ` Gabriel Kerneis
2014-01-14 13:23 ` François Bobot
2014-01-14 13:27 ` Thomas Gazagnaire
2014-01-14 14:06 ` Markus Mottl
2014-01-14 14:12 ` Simon Cruanes
2014-01-14 14:55 ` Amir Chaudhry
2014-01-14 15:09 ` François Bobot
2014-01-14 15:11 ` Anil Madhavapeddy [this message]
2014-01-13 16:42 ` Yotam Barnoy
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=02078ABC-03C2-44C8-99FA-D7FA7E492BA7@recoil.org \
--to=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=francois.bobot@cea.fr \
--cc=simon.cruanes.2007@m4x.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 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 NNTP newsgroup(s).