From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: ocamlnet-devel <ocamlnet-devel@lists.sourceforge.net>
Cc: caml-list <caml-list@inria.fr>
Subject: [Caml-list] [ANN] ocamlnet-4.0.2
Date: Thu, 26 Feb 2015 14:05:00 +0100 [thread overview]
Message-ID: <1424955900.23461.27.camel@e130.lan.sumadev.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
Hi,
just released ocamlnet-4.0.2, with some bug fixes (one important).
Note that I had to change the type of Uq_engines.engine (new method
request_proxy_notification). If you define your own engines, this may
break your builds. Most users won't be affected by this, though.
Download, changelog and other links under
http://projects.camlcity.org/projects/ocamlnet.html
Gerd
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2015-02-26 13:05 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=1424955900.23461.27.camel@e130.lan.sumadev.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=ocamlnet-devel@lists.sourceforge.net \
/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).