From: Xavier Leroy <xavier.leroy@inria.fr>
To: Alessandro Baretta <alex@baretta.com>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Talk about upcoming release
Date: Fri, 12 Jul 2002 16:13:56 +0200 [thread overview]
Message-ID: <20020712161356.A28684@pauillac.inria.fr> (raw)
In-Reply-To: <3D2DF565.5080509@baretta.com>; from alex@baretta.com on Thu, Jul 11, 2002 at 11:15:17PM +0200
> > With all the talk about an upcoming release of OCaml 3.05...
> Well, can anyone whisper a date for the official release? I
> can't wait for it.
The current plan is end of July, if everything goes well.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2002-07-12 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 21:15 Alessandro Baretta
2002-07-11 21:27 ` Jérôme Marant
2002-07-12 14:13 ` Xavier Leroy [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=20020712161356.A28684@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=alex@baretta.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).