From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml Forge and Github
Date: Mon, 30 Sep 2013 00:44:57 +0000 (UTC) [thread overview]
Message-ID: <slrnl4hici.ntq.sylvain@le-gall.net> (raw)
In-Reply-To: <CAHvkLrMk8M68AM8co_09QZ=fYBo3b7HFRu510nF2xFq2sZU6RA@mail.gmail.com>
On 29-09-2013, Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr> wrote:
> Do you know if there is support for GIT on OCaml Forge ?
>
There is git on the forge.
I have some projects on github and tend to only host the source code on
either github or forge.ocamlcore.org. However for website, bug tracking,
mailing lists and releases I do prefer to continue having them on
forge.ocamlcore.org.
Regards
Sylvain
> If such a support exists, you can just convert your SVN repo to GIT on
> OCaml Forge, and mirror your new repo on GitHub. You can then decide
> for example to work on the GIT repo of GitHub, and have a script
> automatically update and push any modification on GitHub to OCaml
> Forge. Git makes having several such repos very easy to administrate
> and synchronise.
>
> --Fabrice
>
>
> On Sun, Sep 29, 2013 at 1:13 PM, Dario Teixeira <darioteixeira@yahoo.com> wrote:
>> Hi,
>>
>> I have a number of projects hosted on the OCaml Forge (thank you Sylvain!),
>> and the hosting includes the Subversion repository for each project. It is,
>> however, harder and harder to resist the allure of Github, particularly when
>> people sending me patches explicitly mention they would prefer to interact
>> through it. I have no complaints about the Forge, though, and I find it a
>> very useful service. However, I would of course also like to accommodate
>> the Github crowd.
>>
>> My default approach would be to convert and migrate the SVN repos to Github,
>> keeping on the Forge only the webpage, file releases, and news. But I'm
>> curious: how did other projects deal with this situation? Is there some other
>> approach the community would find preferable?
>>
>> Thanks for your time + best regards,
>> Dario Teixeira
>>
>>
>> --
>> Caml-list mailing list. Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
>
> --
> Fabrice LE FESSANT
> Chercheur en Informatique
> INRIA Paris Rocquencourt -- OCamlPro
> Programming Languages and Distributed Systems
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
Cheers,
Sylvain Le Gall
--
Website: http://sylvain.le-gall.net/
OCaml forge: http://forge.ocamlcore.org
OCaml blogs: http://planet.ocaml.org
next prev parent reply other threads:[~2013-09-30 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 17:13 Dario Teixeira
2013-09-29 21:53 ` Fabrice Le Fessant
2013-09-30 0:44 ` Sylvain Le Gall [this message]
2013-09-30 11:48 ` Dario Teixeira
2013-09-30 12:39 ` Sylvain Le Gall
2013-09-30 10:36 ` Dario Teixeira
2013-09-30 0:43 ` Anil Madhavapeddy
2013-09-30 11:18 ` Dario Teixeira
2013-09-30 10:44 ` Paolo Donadeo
2013-09-30 10:48 ` Anil Madhavapeddy
2013-09-30 14:20 ` Sylvain Le Gall
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=slrnl4hici.ntq.sylvain@le-gall.net \
--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