From: Erik Martin-Dorel <e.mdorel@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] [ANN] Release of Learn-OCaml (ocaml-sf/learn-ocaml:0.13.0)
Date: Wed, 6 Oct 2021 03:06:07 +0200 [thread overview]
Message-ID: <CAM3h76BdpA+dshR-3cHb=ZxNZT6c7E9t7=k=rOv_+psLze57FQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
Dear list,
FYI the version 0.13.0 of Learn-OCaml has just been released:
- on GitHub, with the corresponding release assets:
https://github.com/ocaml-sf/learn-ocaml/releases/tag/v0.13.0
- on Docker Hub:
https://hub.docker.com/r/ocamlsf/learn-ocaml
- and more details are available from my Discourse post:
https://discuss.ocaml.org/t/ann-release-of-ocaml-sf-learn-ocaml-0-13-0/8577
)
Kind regards,
Erik
--
Érik Martin-Dorel
http://erik.martin-dorel.org/
[-- Attachment #2: Type: text/html, Size: 1077 bytes --]
next reply other threads:[~2021-10-06 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 1:06 Erik Martin-Dorel [this message]
2021-10-06 1:50 ` Alexandre N.
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='CAM3h76BdpA+dshR-3cHb=ZxNZT6c7E9t7=k=rOv_+psLze57FQ@mail.gmail.com' \
--to=e.mdorel@gmail.com \
--cc=caml-list@inria.fr \
--cc=erik.martin-dorel@ens-lyon.org \
/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).