From: Maxence Guesdon <maxence.guesdon@inria.fr>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ocaml code for Okasaki's "Purely Functional Data Structures"
Date: Thu, 6 Dec 2007 15:33:52 +0100 [thread overview]
Message-ID: <20071206153352.7c6a777c@alcazar.inria.fr> (raw)
In-Reply-To: <200712060902.01266.jon@ffconsultancy.com>
On Thu, 6 Dec 2007 09:02:01 +0000
Jon Harrop <jon@ffconsultancy.com> wrote:
> On Thursday 06 December 2007 09:03, Maxence Guesdon wrote:
> > The better way to have the hump updated is to
> > - send an email to hump@caml.inria.fr,
> > - or announce new software or updates on the caml-list, so I can add it to
> > or update the hump.
>
> Is the hump for open source software or free software or all software?
I think it's for software whose code is available.
Regards,
Maxence Guesdon
prev parent reply other threads:[~2007-12-06 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 10:50 Erik de Castro Lopo
2007-12-05 10:54 ` [Caml-list] " Stéphane Lescuyer
2007-12-05 18:20 ` Erik de Castro Lopo
2007-12-05 11:01 ` Paolo Donadeo
2007-12-05 16:03 ` Ashish Agarwal
2007-12-06 9:03 ` Maxence Guesdon
2007-12-06 9:02 ` Jon Harrop
2007-12-06 14:33 ` Maxence Guesdon [this message]
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=20071206153352.7c6a777c@alcazar.inria.fr \
--to=maxence.guesdon@inria.fr \
--cc=caml-list@yquem.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