caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Edgar Friendly <thelema314@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] About the "mingw" port of OCaml
Date: Thu, 15 Dec 2011 15:52:39 -0500	[thread overview]
Message-ID: <CAL-jcAn0Gy7j0tKn7E-366zTbAGtu3ioguAYAsYBRznyysJHfg@mail.gmail.com> (raw)
In-Reply-To: <CAL-jcAkt7grC0z7_dVj7zD846zhHdPjWpHZZeCw_m1iEoBf4Fw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

Reply inline

On Thu, Dec 15, 2011 at 2:20 PM, ygrek <ygrekheretix@gmail.com> wrote:

> On Tue, 13 Dec 2011 08:34:55 -0500
> Edgar Friendly <thelema314@gmail.com> wrote:
>
> > Hmm, I wonder how much the community would benefit from automated
> > testing of ocaml packages under a variety of environments.  Batteries is
> > definitely benefiting from ygrek's jenkins/hudson server[1] (although it
> > must have stopped sending me emails again, as batteries HEAD is unhappy
> > and I didn't get notification).
> >
> > ygrek: could you use more build slaves?
>
> Sure I could, but I do not have extra hardware resources.


Do all the jenkins build slaves have to be in the same place?  I assumed it
was possible to add remote systems to a jenkins server as build hosts.  If
this isn't possible, maybe there's someone who wants to contribute to
better testing of OCaml packages willing to increase your electricity bill
by sending you some hardware.  :)


> Also setting up ocaml
> on windows is a daunting and frustrating exercise, especially so because
> some
> other libs are needed too (pcre, camomile, etc).
>
> Batteries now no longer depends on camomile (or any other external
library), so that dep is gone.  I agree that it's a big pain to get ocaml
setup on windows, although things aren't too bad once the groundwork is
laid properly.


> Concerning the mail notifications - there are no errors in the logs -
> maybe the
> mails land in gmail's spam folder?


Good call - they were all there.  My mistake.  Hopefully I can keep gmail
from spamming them anymore.

E.

[-- Attachment #2: Type: text/html, Size: 2546 bytes --]

  parent reply	other threads:[~2011-12-15 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 12:10 Alain Frisch
2011-12-12 12:50 ` Matthieu Dubuget
2011-12-13 13:34   ` Edgar Friendly
2011-12-13 13:58     ` Gerd Stolpmann
2011-12-15 19:20     ` ygrek
     [not found]       ` <CAL-jcAkt7grC0z7_dVj7zD846zhHdPjWpHZZeCw_m1iEoBf4Fw@mail.gmail.com>
2011-12-15 20:52         ` Edgar Friendly [this message]
2011-12-17 21:31           ` ygrek
2011-12-19  3:10 ` Romain Beauxis

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=CAL-jcAn0Gy7j0tKn7E-366zTbAGtu3ioguAYAsYBRznyysJHfg@mail.gmail.com \
    --to=thelema314@gmail.com \
    --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).