From: "François Bobot" <francois.bobot@cea.fr>
To: caml-list@inria.fr
Cc: platform <platform@lists.ocaml.org>
Subject: Re: [Caml-list] [ocaml-platform] [ANN] Experiment: OCaml patch review on github.com/ocaml/ocaml
Date: Wed, 26 Mar 2014 10:00:21 +0100 [thread overview]
Message-ID: <53329725.90602@cea.fr> (raw)
In-Reply-To: <CAN6ygO=o5S2kO4cKUR9w6ZY3ec0_okcLS2UgVBVWeoQUVY61Sg@mail.gmail.com>
On 25/03/2014 22:34, Yotam Barnoy wrote:
> This is incredible! Now let's get them all compiling and running unit tests on Travis!
> On Tue, Mar 25, 2014 at 12:40 PM, Anil Madhavapeddy <anil@recoil.org <mailto:anil@recoil.org>> wrote:
> Each switch corresponds to the current development trunk, with the
> diff in the PR applied. If the patch is sane, you can proceed to
> install OPAM packages in the experimental tree as usual without
> affecting your day-to-day compiler switch.
>
> Hope this is useful! More details at:
> http://anil.recoil.org/2014/03/25/ocaml-github-and-opam.html
It is awfully useful. I was trying to setup an OPAM repository for simplifying the review of PR#22,
but you did it for me and all the others, thank you.
I'm just wondering if it is wise to add all these switches to the default OPAM repository. For
casual ocaml user the useful switches are lost among all these PR.
Perhaps the default possible switches can be reduced to the last releases (for people that work on
project that must support old version of ocaml) and to the beta and trunk for people that are
curious of the accepted new features.
For ocaml compiler hackers a specific OPAM repository with all the svn branches and github PR can
be setup.
What do you think?
--
François
next prev parent reply other threads:[~2014-03-26 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 11:34 [Caml-list] " Gabriel Scherer
2014-03-25 16:40 ` Anil Madhavapeddy
2014-03-25 21:34 ` [Caml-list] [ocaml-platform] " Yotam Barnoy
2014-03-26 9:00 ` François Bobot [this message]
2014-03-26 9:12 ` Louis Gesbert
2014-03-26 9:37 ` Anil Madhavapeddy
2014-04-08 12:37 ` Jeremy Yallop
2014-04-08 12:59 ` Jacques-Pascal Deplaix
2014-04-08 13:35 ` Gabriel Scherer
2014-04-08 13:39 ` Anil Madhavapeddy
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=53329725.90602@cea.fr \
--to=francois.bobot@cea.fr \
--cc=caml-list@inria.fr \
--cc=platform@lists.ocaml.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).