caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Github OCaml mirror available
Date: Thu, 29 Nov 2012 10:09:01 +0000	[thread overview]
Message-ID: <52F1AA86-D843-4AB5-B8DF-1FFBFAC4E2B9@recoil.org> (raw)

There have been quite a few Git mirrors of the OCaml compiler tree floating around for the past few years.  I've grabbed the "OCaml" organisation on Github, where key community projects can be hosted such as OASIS, the ocaml.org website, and a mirror of the compiler itself.

You can find it at:
http://github.com/ocaml/ocaml

The conversion scripts were based on Benedikt Meurer's very useful guide, with the exception that SVN tags and branches are converted into native Git tags, and an authors file exists.  You can find the scripts that drive it here:
https://github.com/ocaml/ocaml.org-scripts/tree/master/vcs-sync/svn-ocaml

For those concerned about Github being a proprietary service, I'm also setting up a git.ocaml.org mirror of all the repositories hosted on Github.  This will be ready in a few weeks.  Note that the compiler Git repository is a *read-only mirror*, and that all active development occurs within the INRIA SVN, and issues should continue to be reported via Mantis: 

http://caml.inria.fr/mantis

Thanks to Leo White and Christophe Troestler for helping with getting this working!  Please consider this experimental for a few weeks in case any issues come up with the scripts that cause us to delete the repository and recreate it.  If anyone feels strongly about needing a Mercurial mirror, please also get in touch.

-anil


                 reply	other threads:[~2012-11-29 10:09 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=52F1AA86-D843-4AB5-B8DF-1FFBFAC4E2B9@recoil.org \
    --to=anil@recoil.org \
    --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).