From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: Re: Caml-inspect library
Date: Thu, 15 Apr 2010 15:25:37 +0000 (UTC) [thread overview]
Message-ID: <slrnhsebvh.bpc.sylvain@gallu.homelinux.org> (raw)
In-Reply-To: <1B8DE757-E700-4744-8EFD-FE6F03707E59@gmail.com>
Hello,
On 15-04-2010, Kaspar Rohrer <kaspar.rohrer@gmail.com> wrote:
>
> I hope nobody takes offense over the fact that I chose Github over
> Forge.ocamlcore.org.
Not at all, github is shiny and efficient to manage a git repository.
A good solution, is to host your git/bug tracking on github and download
section/website/news/mailing list on a forge.ocamlcore.org project. You
just have to remove the "SCM" tab and redirect the homepage to github or
write your own project homepage and put a link to github there.
This way you can benefit of the best of each hosting service.
Good luck with ocaml-inspect.
Regards,
Sylvain Le Gall
ps: maybe one day we will be able to integrate nicely github with
forge.ocamlcore.org and you will just have to hit the button "Share my
projects on github through forge.ocamlcore.org"... Any taker send me an
email ;-)
prev parent reply other threads:[~2010-04-15 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 15:12 Kaspar Rohrer
2010-04-15 15:25 ` Sylvain Le Gall [this message]
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=slrnhsebvh.bpc.sylvain@gallu.homelinux.org \
--to=sylvain@le-gall.net \
--cc=caml-list@inria.fr \
/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).