Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "lwn" <lwn@lwn.net>, caml-list@inria.fr
Subject: [Caml-list] Attn: Development Editor, Latest OCaml Weekly News
Date: Tue, 17 Mar 2026 15:39:05 +0100	[thread overview]
Message-ID: <m2341ymsfq.fsf@mac-03220211.irisa.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 16376 bytes --]

Hello

Here is the latest OCaml Weekly News, for the week of March 10 to 17,
2026.

Table of Contents
─────────────────

Public securiy meeting
Google OR-Tools: CP-SAT Subset
Neocaml-mode (A modern Emacs major mode for OCaml) is looking for testers
oui: multi-platform binary installers
Nixtamal: Fulfilling Input Pinning for Nix
OCaml-RDF 1.2.0
Slipshow!
Is there a public archive for the caml-list?
Old CWN


Public securiy meeting
══════════════════════

  Archive: <https://discuss.ocaml.org/t/public-securiy-meeting/17882/1>


Hannes Mehnert announced
────────────────────────

  Dear everyone,

  as a reminder – next week Thursday (March 19th) 14:00 CEST, there will
  be a public OCaml security meeting hosted by the
  <https://ocaml.org/security> team. We will meet at
  <https://meet.bornhack.dk/OCamlSecurityPublicMeeting>

  Our agenda and notes will be at
  <https://pad.data.coop/Ie5voBePSiKvjZdEko6otQ>#

  If you're curious, the notes from our last meeting are at
  <https://pad.data.coop/7-Ic5rG6ToynsW02hJsndg>

  Hope to see you there!


Google OR-Tools: CP-SAT Subset
══════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/google-or-tools-cp-sat-subset/17885/1>


Timothy Bourke announced
────────────────────────

  The [Google OR-Tools] are a suite of tools for solving optimization
  problems. They include, in particular, [CP-SAT], which is a powerful
  constraint solver and optimizer for integer linear programming and
  boolean satisfiability problems.

  The [ocaml-ortools] package provides an OCaml interface to a subset of
  CP-SAT constraints. It comprises two parts `ortools`, which allows
  modelling constraint problems in OCaml and translating them to a
  protocol buffer format (thanks to [ocaml-protc]), and
  `ortools_solvers`, which allows an embedded version of CP-SAT to be
  called directly from OCaml. Both parts can be installed using opam or
  built with dune. The latter includes the source of OR-Tools 9.15 which
  is built together with most of its libraries and installed as part of
  the opam package.

  Some simple examples can be found in the [online documentation] and
  [source code]. They can be built using the following commands.

  ┌────
  │ opam install ortools ortools_solvers
  │ ocamlfind ocamlopt -o prog -package ortools -package ortools_solvers -linkpkg prog.ml
  └────

  I would be happy to accept pull requests for the missing CP-SAT
  constraints (I think it best to develop the interface together with
  real applications, and I only need the ILP and boolean parts at the
  moment), to translate more of the standard example programs (an easy
  way to contribute), and to include other solvers from the suite
  (likely to involve solving tedious compilation and compatibility
  problems across multiple platforms).

  Thanks to @nojb, @Rucikir , and others for [their help] with [dune],
  and @xvw and @panglesd for [their help] with odoc. Thanks to @jmid ,
  @mseri , and @avsm for discussing and merging my [opam-repository]
  pull requests.


[Google OR-Tools] <https://developers.google.com/optimization>

[CP-SAT] <https://d-krupke.github.io/cpsat-primer/>

[ocaml-ortools] <https://github.com/INRIA/ocaml-ortools>

[ocaml-protc] <https://github.com/mransan/ocaml-protoc>

[online documentation]
<https://inria.github.io/ocaml-ortools/ortools/index.html>

[source code]
<https://github.com/INRIA/ocaml-ortools/tree/master/samples/sat>

[their help]
<https://discuss.ocaml.org/t/foreign-archives-no-static-libraries-dylib-on-mac/17669>

[dune] <https://discuss.ocaml.org/t/dune-cmake-and-j/17768>

[their help]
<https://discuss.ocaml.org/t/odoc-index-for-multiple-packages-inter-package-links-and-local-global-sidebar/17652>

[opam-repository] <https://github.com/ocaml/opam-repository>


Neocaml-mode (A modern Emacs major mode for OCaml) is looking for testers
═════════════════════════════════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/neocaml-mode-a-modern-emacs-major-mode-for-ocaml-is-looking-for-testers/17807/23>


Continuing this thread, Bozhidar Batsov announced
─────────────────────────────────────────────────

  FYI - <https://github.com/bbatsov/neocaml/releases/tag/v0.4.0>

  You'll need to update your Tree-sitter grammars due to some upstream
  (breaking) changes in the TS OCaml grammar.


oui: multi-platform binary installers
═════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/ann-oui-multi-platform-binary-installers/17886/1>


Nathan Rebours announced
────────────────────────

  We are happy to announce the first release of `oui'!

  `oui' is a tool that generates multi-platform binary installers for
  your OCaml applications. It can generate installers for Windows, Linux
  and MacOS.  We hope it will help all of you out there developping
  applications for non OCaml developers, allowing your users to install
  your programs without having to install OCaml and/or opam, thus
  greatly simplifying their user experience.

  You can install `oui' with the following command:
  ┌────
  │ opam install oui
  └────

  We made it as generic as possible to ensure it works for everyone. You
  invoke it as follows:
  ┌────
  │ oui build oui.json install-bundle
  └────

  where `install-bundle' is a folder containing your precompiled
  binaries and any files you want to install alongside them, arranged in
  any way you'd like.  The `oui.json' file is a configuration file that
  contains metadata and information on the installation bundle's layout
  such as where to find binaries to add to the `PATH' or where to find
  manpages.

  `oui' can also create installers for plugins, assuming the main
  application was either installed by a `oui' generated installer, or
  was installed following some basic rules.

  The project is hosted on github:
  <https://github.com/OCamlPro/ocaml-universal-installer> The full
  documentation is available [here]. In particular, you can find
  guidelines on how to use it to create installers for your dune built
  project [here].

  Please go ahead and give it a try, we'd love to hear your feedback.

  We welcome external contributors so if you'd like to take part in the
  project, please read our [CONTRIBUTING.md] and jump in!

  The project is still in a relatively early stage and there are some
  key features we'd like to add, such as streamlining the user
  experience for dune projects (removing the necessity to maintain a
  separate configuration file for the most common use cases) or support
  for cross-compilation/cross-platform installer generation. If those
  features sound interesting to you and you would like to fund their
  development, please reach out to contact@ocamlpro.com .

  Finally, we'd like to thank our partner CEA-list who funded the
  initial development of `oui' from `opam-wix' and made it all possible!

  Happy installing!


[here]
<https://github.com/OCamlPro/ocaml-universal-installer/blob/master/doc/README.md>

[here]
<https://github.com/OCamlPro/ocaml-universal-installer/blob/master/doc/README.md#generating-a-binary-installer-for-your-dune-project>

[CONTRIBUTING.md]
<https://github.com/OCamlPro/ocaml-universal-installer/blob/master/CONTRIBUTING.md>


Nixtamal: Fulfilling Input Pinning for Nix
══════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/ann-nixtamal-fulfilling-input-pinning-for-nix/17887/1>


toastal announced
─────────────────

  [Nixtamal] is my first serious OCaml project release, now at verison
  1.1.4. It was created as a reaction to the lack of features I wanted
  from its “competitors” `niv' & `npins' while additionally covering
  features Nix flakes never could support given it’s rigid design
  philosophy which has more drawbacks than folks initially realize. I
  have been using it on all projects for a couple months now & had at
  least a couple folks I didn’t know prior try it out providing feedback
  & bug reports.

  *Key features:*

  • Automate the manual work of input pinning for dependency management
  • Allow easy ways to lock & refresh those inputs
  • Declarative [KDL] manifest file over imperative <abbr title="command
    line interface">CLI</abbr> flags
  • Host, forge, <abbr title="version control
    system">VCS</abbr>-agnostic
  • Choose <abbr title="evaluation">eval</abbr> time fetchers (builtins)
    or build time fetchers (Nixpkgs, default) — which opens up fetching
    now-supported [Darcs], [Pijul], & [Fossil]
  • Supports mirrors (on kinds that support mirrors)
  • Override hash algorithm on a per-project & per-input basis —
    including BLAKE3 support (which _does_ require enabling
    `blake3-hashes` to opt in)
  • Custom freshness commands (avoid refetching massive inputs just to
    check the hash hasn’t changed)
  • No experimental Nix features required (flakes)

  Outside the homepage, it would be worth checking the [<abbr
  title="frequently asked questions">FAQs</abbr>] if any /whats/ or
  /whys/ come up.


[Nixtamal] <https://nixtamal.toast.al>

[KDL] <https://kdl.dev>

[Darcs] <https://darcs.net>

[Pijul] <https://pijul.org>

[Fossil] <https://fossil-scm.org>

[<abbr title="frequently asked questions">FAQs</abbr>]
<https://nixtamal.toast.al/faqs/>


OCaml-RDF 1.2.0
═══════════════

  Archive: <https://discuss.ocaml.org/t/ann-ocaml-rdf-1-2-0/17890/1>


Zoggy announced
───────────────

  Hello,

  A new release of OCaml-RDF, [1.2.0], is available. The main additions
  are:

  • a new [Igraph] module, providing immutable graphs (for functional
    style).
  • a new [rdf_rdfa] package implementing a [Rdfa 1.1] processor.

  It is available from [my own opam repository].


[1.2.0] <https://www.good-eris.net/ocaml-rdf/posts/ocaml-rdf-1.2.0.html>

[Igraph]
<https://www.good-eris.net/ocaml-rdf/refdoc/rdf/Rdf/Igraph/index.html>

[rdf_rdfa]
<https://www.good-eris.net/ocaml-rdf/refdoc/rdf_rdfa/index.html>

[Rdfa 1.1] <https://www.w3.org/TR/rdfa-core>

[my own opam repository] <https://framagit.org/zoggy/opam-repository>


Slipshow!
═════════

  Archive: <https://discuss.ocaml.org/t/ann-slipshow/16337/22>


Continuing this thread, Paul-Elliot announced
─────────────────────────────────────────────

  It is with a blatant denial of the current situation that I announce
  the next release of Slipshow:


Slipshow 0.10.0: Don't look `{up}'
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  The +asteroid+ star of the release is the new warnings that the
  compiler can raise to help you write a bug-free presentation. Those
  warnings are visible on the command-line, but also in the
  hot-reloading preview in `serve' mode!

  <https://github.com/user-attachments/assets/f78568e5-dbbf-49e3-9cd3-8d2e5c4edfda>

  Warnings will hopefully help detect bugs in your presentations and
  improve the experience, especially of newcomers!

  This time, I'd like to thanks @Alistair for the incredible [Grace 💅]
  library. Whenever I look somewhere, I find a new OCaml pearl. Thank
  you for that! This library, the ecosystem, open-source, are all
  awesome things.

  And thanks again to NLNet for [supporting] the development of
  Slipshow!

  Here is the full changelog:


[Grace 💅] <https://github.com/johnyob/grace>

[supporting] <https://nlnet.nl/project/Slipshow/>


Added
╌╌╌╌╌

  • Helpful warnings at compile-time (#213):
    • Action parsing failures,
    • Missing ID (and `external-ids' frontmatter field to selectively
      deactivate),
    • Duplicated ID,
    • Frontmatter parsing error,
    • Wrong target type for actions,
    • Missing file,
    • Unknown attribute,
    • …


Fixed
╌╌╌╌╌

  • Fixed drawing stopping slightly after pauses (#216)
  • Fixed keyboard shortcuts not working in serve mode until the preview
    was clicked (#215)
  • Fix shortcuts not working after saving a drawing (#217)
  • Fix wrong example links in docs (#218)


Is there a public archive for the caml-list?
════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/is-there-a-public-archive-for-the-caml-list/16374/6>


Continuing this thread, Calascibetta Romain announced
─────────────────────────────────────────────────────

  Hello, I am pleased to announce the launch of
  <https://caml-list.robur.coop/>, a unikernel that provides a search
  engine for the caml-list. We now have public access to this archive
  :tada:!

  Our cooperative is currently working on several fronts, including
  email, by offering an archiving system. For more details, please see
  [this article]. Another article describes [the search engine] we use,
  and a third explains [how we developed this unikernel] (although the
  latter has evolved considerably since then, the core remains the
  same).

  We are therefore delighted to make this service available to the
  community, and if you would like to help us improve it, the project is
  currently available [here]. We would like to thank [NLnet] for funding
  this unikernel, and if you appreciate our work, please do not hesitate
  to make a donation to our cooperative (via [GitHub] or [directly to
  our cooperative])

  Finally, this example also showcases all our work on unikernels: from
  what an Ethernet frame is, through the archive system and the
  extraction of emails from a virtualised hard drive, right up to the
  HTTP request - *everything is done in OCaml* (and we would once again
  recommend reading our tutorial on [mnet] if you would like to build up
  unikernels).

  So have fun hunting for relics from the history of OCaml!


[this article]
<https://blog.robur.coop/articles/2025-01-07-carton-and-cachet.html>

[the search engine]
<https://blog.robur.coop/articles/ptt_stem_and_search_engine.html>

[how we developed this unikernel]
<https://blog.robur.coop/articles/2025-04-12-ptt-search-webapp.html>

[here] <https://github.com/robur-coop/blame>

[NLnet] <https://nlnet.nl/>

[GitHub] <https://github.com/sponsors/robur-coop>

[directly to our cooperative] <https://robur.coop/Donate>

[mnet] <https://robur-coop.github.io/mnet/>


Old CWN
═══════

  If you happen to miss a CWN, you can [send me a message] and I'll mail
  it to you, or go take a look at [the archive] or the [RSS feed of the
  archives].

  If you also wish to receive it every week by mail, you may subscribe
  to the [caml-list].

  [Alan Schmitt]


[send me a message] <mailto:alan.schmitt@polytechnique.org>

[the archive] <https://alan.petitepomme.net/cwn/>

[RSS feed of the archives] <https://alan.petitepomme.net/cwn/cwn.rss>

[caml-list] <https://sympa.inria.fr/sympa/info/caml-list>

[Alan Schmitt] <https://alan.petitepomme.net/>


[-- Attachment #2: Type: text/html, Size: 27639 bytes --]

             reply	other threads:[~2026-03-17 14:39 UTC|newest]

Thread overview: 284+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 14:39 Alan Schmitt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-10 13:30 Alan Schmitt
2026-03-03 13:54 Alan Schmitt
2026-02-24 13:36 Alan Schmitt
2026-02-17 13:47 Alan Schmitt
2026-02-10 10:36 Alan Schmitt
2026-02-03 10:04 Alan Schmitt
2026-01-27 12:41 Alan Schmitt
2026-01-20  9:19 Alan Schmitt
2026-01-13  8:27 Alan Schmitt
2026-01-06 13:14 Alan Schmitt
2025-12-30  9:33 Alan Schmitt
2025-12-23 11:00 Alan Schmitt
2025-12-16 13:30 Alan Schmitt
2025-12-09 15:04 Alan Schmitt
2025-12-02 10:39 Alan Schmitt
2025-11-25 13:49 Alan Schmitt
2025-11-18 14:01 Alan Schmitt
2025-11-11  9:49 Alan Schmitt
2025-11-04 13:21 Alan Schmitt
2025-10-28 13:30 Alan Schmitt
2025-10-21  9:17 Alan Schmitt
2025-10-14  9:56 Alan Schmitt
2025-10-07 12:22 Alan Schmitt
2025-09-30 13:12 Alan Schmitt
2025-09-23 13:23 Alan Schmitt
2025-09-16 11:52 Alan Schmitt
2025-09-09 12:30 Alan Schmitt
2025-09-02 12:23 Alan Schmitt
2025-08-26 12:34 Alan Schmitt
2025-08-19 12:20 Alan Schmitt
2025-08-12 15:32 Alan Schmitt
2025-08-05  8:17 Alan Schmitt
2025-07-29  9:36 Alan Schmitt
2025-07-22 12:07 Alan Schmitt
2025-07-15 17:14 Alan Schmitt
2025-07-08 12:45 Alan Schmitt
2025-07-01 11:16 Alan Schmitt
2025-06-24 14:02 Alan Schmitt
2025-06-17  6:44 Alan Schmitt
2025-06-10 13:36 Alan Schmitt
2025-06-03  9:19 Alan Schmitt
2025-05-27  9:22 Alan Schmitt
2025-05-20 11:52 Alan Schmitt
2025-05-13  9:40 Alan Schmitt
2025-05-06  7:24 Alan Schmitt
2025-04-29  8:39 Alan Schmitt
2025-04-22 11:50 Alan Schmitt
2025-04-15  9:51 Alan Schmitt
2025-04-08 13:14 Alan Schmitt
2025-04-01  9:12 Alan Schmitt
2025-03-25  8:06 Alan Schmitt
2025-03-18 10:18 Alan Schmitt
2025-03-11 15:00 Alan Schmitt
2025-03-04 14:01 Alan Schmitt
2025-02-25 10:36 Alan Schmitt
2025-02-18 14:33 Alan Schmitt
2025-02-11  7:17 Alan Schmitt
2025-02-04 12:05 Alan Schmitt
2025-01-28 13:24 Alan Schmitt
2025-01-21 15:47 Alan Schmitt
2025-01-14  8:20 Alan Schmitt
2025-01-07 17:26 Alan Schmitt
2024-12-31  8:03 Alan Schmitt
2024-12-24  8:55 Alan Schmitt
2024-12-17 13:05 Alan Schmitt
2024-12-10 13:48 Alan Schmitt
2024-12-03 14:44 Alan Schmitt
2024-11-26  8:30 Alan Schmitt
2024-11-19  6:52 Alan Schmitt
2024-11-12 15:00 Alan Schmitt
2024-11-05 13:22 Alan Schmitt
2024-10-29 13:30 Alan Schmitt
2024-10-22 12:42 Alan Schmitt
2024-10-15 13:31 Alan Schmitt
2024-10-08 10:56 Alan Schmitt
2024-10-01 13:37 Alan Schmitt
2024-09-24 13:18 Alan Schmitt
2024-09-17 14:02 Alan Schmitt
2024-09-10 13:55 Alan Schmitt
2024-09-03  8:24 Alan Schmitt
2024-08-27  9:02 Alan Schmitt
2024-08-20  9:29 Alan Schmitt
2024-08-13 13:21 Alan Schmitt
2024-08-06  9:00 Alan Schmitt
2024-07-30 13:26 Alan Schmitt
2024-07-23 13:30 Alan Schmitt
2024-07-16  6:24 Alan Schmitt
2024-07-09  9:19 Alan Schmitt
2024-07-02  7:30 Alan Schmitt
2024-06-25 13:58 Alan Schmitt
2024-06-18 13:05 Alan Schmitt
2024-06-11 15:04 Alan Schmitt
2024-06-04 13:26 Alan Schmitt
2024-05-28  9:07 Alan Schmitt
2024-05-21 13:07 Alan Schmitt
2024-05-14 13:25 Alan Schmitt
2024-05-07  7:30 Alan Schmitt
2024-04-30  7:22 Alan Schmitt
2024-04-23 12:17 Alan Schmitt
2024-04-16 12:00 Alan Schmitt
2024-04-09  9:15 Alan Schmitt
2024-04-02 14:31 Alan Schmitt
2024-03-26  6:32 Alan Schmitt
2024-03-19 15:09 Alan Schmitt
2024-03-12 10:31 Alan Schmitt
2024-03-05 14:50 Alan Schmitt
2024-02-27 13:53 Alan Schmitt
2024-02-20  9:12 Alan Schmitt
2024-02-13  8:42 Alan Schmitt
2024-02-06 15:14 Alan Schmitt
2024-01-30 14:16 Alan Schmitt
2024-01-23  9:45 Alan Schmitt
2024-01-16 10:01 Alan Schmitt
2024-01-09 13:40 Alan Schmitt
2024-01-02  8:59 Alan Schmitt
2023-12-26 10:12 Alan Schmitt
2023-12-19 10:10 Alan Schmitt
2023-12-12 10:20 Alan Schmitt
2023-12-05 10:13 Alan Schmitt
2023-11-28  9:09 Alan Schmitt
2023-11-21  7:47 Alan Schmitt
2023-11-14 13:42 Alan Schmitt
2023-11-07 10:31 Alan Schmitt
2023-10-31 10:43 Alan Schmitt
2023-10-24  9:17 Alan Schmitt
2023-10-17  7:46 Alan Schmitt
2023-10-10  7:48 Alan Schmitt
2023-10-03 13:00 Alan Schmitt
2023-09-19  8:54 Alan Schmitt
2023-09-12 13:21 Alan Schmitt
2023-09-05  9:00 Alan Schmitt
2023-08-29 13:04 Alan Schmitt
2023-08-22  9:20 Alan Schmitt
2023-08-15 16:33 Alan Schmitt
2023-08-08  8:53 Alan Schmitt
2023-08-01  7:13 Alan Schmitt
2023-07-25  8:45 Alan Schmitt
2023-07-11  8:45 Alan Schmitt
2023-07-04  9:18 Alan Schmitt
2023-06-27  8:38 Alan Schmitt
2023-06-20  9:52 Alan Schmitt
2023-06-13  7:09 Alan Schmitt
2023-06-06 14:22 Alan Schmitt
2023-05-30 15:43 Alan Schmitt
2023-05-23  9:41 Alan Schmitt
2023-05-16 13:05 Alan Schmitt
2023-05-09 11:49 Alan Schmitt
2023-05-02  8:01 Alan Schmitt
2023-04-25  9:25 Alan Schmitt
2023-04-18  8:50 Alan Schmitt
2023-04-11 12:41 Alan Schmitt
2023-04-04  8:45 Alan Schmitt
2023-03-28  7:21 Alan Schmitt
2023-03-21 10:07 Alan Schmitt
2023-03-14  9:52 Alan Schmitt
2023-03-07  9:02 Alan Schmitt
2023-02-28 14:38 Alan Schmitt
2023-02-21 10:19 Alan Schmitt
2023-02-14  8:12 Alan Schmitt
2023-02-07  8:16 Alan Schmitt
2023-01-31  6:44 Alan Schmitt
2023-01-24  8:57 Alan Schmitt
2023-01-17  8:37 Alan Schmitt
2022-11-29 14:53 Alan Schmitt
2022-09-27  7:17 Alan Schmitt
2022-09-20 14:01 Alan Schmitt
2022-09-13  8:40 Alan Schmitt
2022-08-23  8:06 Alan Schmitt
2022-08-16  8:51 Alan Schmitt
2022-08-09  8:02 Alan Schmitt
2022-08-02  9:51 Alan Schmitt
2022-07-26 17:54 Alan Schmitt
2022-07-19  8:58 Alan Schmitt
2022-07-12  7:59 Alan Schmitt
2022-07-05  7:42 Alan Schmitt
2022-06-28  7:37 Alan Schmitt
2022-06-21  8:06 Alan Schmitt
2022-06-14  9:29 Alan Schmitt
2022-06-07 10:15 Alan Schmitt
2022-05-31 12:29 Alan Schmitt
2022-05-24  8:04 Alan Schmitt
2022-05-17  7:12 Alan Schmitt
2022-05-10 12:30 Alan Schmitt
2022-05-03  9:11 Alan Schmitt
2022-04-26  6:44 Alan Schmitt
2022-04-19  5:34 Alan Schmitt
2022-04-12  8:10 Alan Schmitt
2022-04-05 11:50 Alan Schmitt
2022-03-29  7:42 Alan Schmitt
2022-03-22 13:01 Alan Schmitt
2022-03-15  9:59 Alan Schmitt
2022-03-01 13:54 Alan Schmitt
2022-02-22 12:43 Alan Schmitt
2022-02-08 13:16 Alan Schmitt
2022-02-01 13:00 Alan Schmitt
2022-01-25 12:44 Alan Schmitt
2022-01-11  8:20 Alan Schmitt
2022-01-04  7:56 Alan Schmitt
2021-12-28  8:59 Alan Schmitt
2021-12-21  9:11 Alan Schmitt
2021-12-14 11:02 Alan Schmitt
2021-11-30 10:51 Alan Schmitt
2021-11-16  8:41 Alan Schmitt
2021-11-09 10:08 Alan Schmitt
2021-11-02  8:50 Alan Schmitt
2021-10-19  8:23 Alan Schmitt
2021-09-28  6:37 Alan Schmitt
2021-09-21  9:09 Alan Schmitt
2021-09-07 13:23 Alan Schmitt
2021-08-24 13:44 Alan Schmitt
2021-08-17  6:24 Alan Schmitt
2021-08-10 16:47 Alan Schmitt
2021-07-27  8:54 Alan Schmitt
2021-07-20 12:58 Alan Schmitt
2021-07-06 12:33 Alan Schmitt
2021-06-29 12:24 Alan Schmitt
2021-06-22  9:04 Alan Schmitt
2021-06-01  9:23 Alan Schmitt
2021-05-25  7:30 Alan Schmitt
2021-05-11 14:47 Alan Schmitt
2021-05-04  8:57 Alan Schmitt
2021-04-27 14:26 Alan Schmitt
2021-04-20  9:07 Alan Schmitt
2021-04-06  9:42 Alan Schmitt
2021-03-30 14:55 Alan Schmitt
2021-03-23  9:05 Alan Schmitt
2021-03-16 10:31 Alan Schmitt
2021-03-09 10:58 Alan Schmitt
2021-02-23  9:51 Alan Schmitt
2021-02-16 13:53 Alan Schmitt
2021-02-02 13:56 Alan Schmitt
2021-01-26 13:25 Alan Schmitt
2021-01-19 14:28 Alan Schmitt
2021-01-12  9:47 Alan Schmitt
2021-01-05 11:22 Alan Schmitt
2020-12-29  9:59 Alan Schmitt
2020-12-22  8:48 Alan Schmitt
2020-12-15  9:51 Alan Schmitt
2020-12-01  8:54 Alan Schmitt
2020-11-03 15:15 Alan Schmitt
2020-10-27  8:43 Alan Schmitt
2020-10-20  8:15 Alan Schmitt
2020-10-06  7:22 Alan Schmitt
2020-09-29  7:02 Alan Schmitt
2020-09-22  7:27 Alan Schmitt
2020-09-08 13:11 Alan Schmitt
2020-09-01  7:55 Alan Schmitt
2020-08-18  7:25 Alan Schmitt
2020-07-28 16:57 Alan Schmitt
2020-07-21 14:42 Alan Schmitt
2020-07-14  9:54 Alan Schmitt
2020-07-07 10:04 Alan Schmitt
2020-06-30  7:00 Alan Schmitt
2020-06-16  8:36 Alan Schmitt
2020-06-09  8:28 Alan Schmitt
2020-05-19  9:52 Alan Schmitt
2020-05-12  7:45 Alan Schmitt
2020-05-05  7:45 Alan Schmitt
2020-04-28 12:44 Alan Schmitt
2020-04-21  8:58 Alan Schmitt
2020-04-14  7:28 Alan Schmitt
2020-04-07  7:51 Alan Schmitt
2020-03-31  9:54 Alan Schmitt
2020-03-24  9:31 Alan Schmitt
2020-03-17 11:04 Alan Schmitt
2020-03-10 14:28 Alan Schmitt
2020-03-03  8:00 Alan Schmitt
2020-02-25  8:51 Alan Schmitt
2020-02-18  8:18 Alan Schmitt
2020-02-04  8:47 Alan Schmitt
2020-01-28 10:53 Alan Schmitt
2020-01-21 14:08 Alan Schmitt
2020-01-14 14:16 Alan Schmitt
2020-01-07 13:43 Alan Schmitt
2019-12-31  9:18 Alan Schmitt
2019-12-17  8:52 Alan Schmitt
2019-12-10  8:21 Alan Schmitt
2019-12-03 15:42 Alan Schmitt
2019-11-26  8:33 Alan Schmitt
2019-11-12 13:21 Alan Schmitt
2019-11-05  6:55 Alan Schmitt
2019-10-15  7:28 Alan Schmitt
2019-09-03  7:35 Alan Schmitt

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=m2341ymsfq.fsf@mac-03220211.irisa.fr \
    --to=alan.schmitt@polytechnique.org \
    --cc=caml-list@inria.fr \
    --cc=lwn@lwn.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