From: Andres Varon <avaron@gmail.com>
To: yminsky@gmail.com
Cc: Jim Miller <gordon.j.miller@gmail.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] caml trading
Date: Mon, 16 Mar 2009 14:55:37 -0400 [thread overview]
Message-ID: <B13C1437-4711-4DDB-ACEA-3104857ED9DB@gmail.com> (raw)
In-Reply-To: <891bd3390903161135xba35405wa62edd7db1706336@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
On Mar 16, 2009, at 2:35 PM, Yaron Minsky wrote:
>
>
> Our blog is here:
>
> http://ocaml.janestreet.com
>
> And I wrote a post about our build system here:
>
> http://ocaml.janestreet.com/?q=node/36
>
> Interestingly, it is the most popular post on the blog. Turns out,
> there are more people who care about version control than people who
> care about functional programming. (It's not that bad, though. The
> second most popular post is on type-indexed values).
Just to add the bit of our own experience here:
We have a relatively small group of people here (at most 5 working on
the same project, some in separate locations). We also moved to
mercurial more than a year ago (we started with subversion), and have
automated tests before and after each commit using buildbot (http://buildbot.net/trac
). Each developer can submit his local changes for test before pushing
to the main repository, to avoid breaking the central repository that
we all pull from. The tests run in numerous processors and OS'es
(including parallel machines using MPI, Linux, Windows, and Mac OS X).
This setup works fantastic for our group (and is not very different
from that of Jane Street). The main weakness was the Makefile (no
wonder). To solve it, few weeks ago I moved all the build scripts to
ocamlbuild, and it is working like a charm now. Our lives are a little
bit better (once again), thanks to the french fellows :-).
Andres
>
> y
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #2: Type: text/html, Size: 2582 bytes --]
next prev parent reply other threads:[~2009-03-16 18:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 19:52 Yaron Minsky
2009-03-14 0:56 ` [Caml-list] " Yoann Padioleau
2009-03-14 17:25 ` Yaron Minsky
2009-03-16 14:24 ` Yoann Padioleau
2009-03-16 14:30 ` Jim Miller
2009-03-16 18:35 ` Yaron Minsky
2009-03-16 18:55 ` Andres Varon [this message]
2009-03-16 15:31 ` Markus Mottl
2009-03-17 2:37 ` David Baelde
2009-03-17 3:06 ` Alexy Khrabrov
2009-03-17 3:22 ` Yaron Minsky
2009-03-17 13:56 ` Markus Mottl
2009-03-17 15:26 ` Mike Lin
2009-03-17 17:14 ` Xavier Leroy
2009-03-17 17:05 ` Lawrence Austen
2009-03-17 22:35 ` xahlee
2009-03-18 10:38 ` Philippe Veber
2009-03-19 9:49 ` Loup Vaillant
2009-03-17 11:34 ` Kuba Ober
2009-03-16 23:23 ` Mike Lin
2009-03-14 7:25 ` Jon Harrop
2009-03-15 18:26 ` Yaron Minsky
2009-03-14 19:30 ` Jim Miller
2009-03-15 18:20 ` Yaron Minsky
2009-03-16 17:01 ` aditya siram
2009-03-16 17:38 ` Jon Harrop
2009-03-17 7:27 ` Philip
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=B13C1437-4711-4DDB-ACEA-3104857ED9DB@gmail.com \
--to=avaron@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=gordon.j.miller@gmail.com \
--cc=yminsky@gmail.com \
/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