From: Stefano Zacchiroli <zack@upsilon.cc>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml version 3.10.2 released
Date: Mon, 3 Mar 2008 11:15:54 +0100 [thread overview]
Message-ID: <20080303101553.GA11631@takhisis.invalid> (raw)
In-Reply-To: <625B7ADE-7ED6-4980-B7EF-B4072CC9992D@inria.fr>
On Fri, Feb 29, 2008 at 01:38:12PM +0100, Damien Doligez wrote:
> It is our pleasure to announce the release of OCaml version 3.10.2.
> This is mainly a bug-fix release, see the list of changes below.
I know generally this is not the case, but out of curiosity: is it
possibly that by chance this release did *not* break the binary
compatibility with objects compiled by OCaml 3.10.1?
Cheers.
--
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{upsilon.cc,cs.unibo.it,debian.org} -<%>- http://upsilon.cc/zack/
(15:56:48) Zack: e la demo dema ? /\ All one has to do is hit the
(15:57:15) Bac: no, la demo scema \/ right keys at the right time
next prev parent reply other threads:[~2008-03-03 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 12:38 Damien Doligez
2008-03-03 10:15 ` Stefano Zacchiroli [this message]
2008-03-03 14:05 ` [Caml-list] " Damien Doligez
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=20080303101553.GA11631@takhisis.invalid \
--to=zack@upsilon.cc \
--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