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, 13 Oct 2026 08:57:47 +0200 [thread overview]
Message-ID: <m24ieqf5p0.fsf@mac-03220211.irisa.fr> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 16692 bytes --]
Hello
Here is the latest OCaml Weekly News, for the week of October 06 to 13,
2026.
Table of Contents
─────────────────
betacalendars 1.0.0 — deterministic date and calendar utilities
Sedlex 3.8.1
opam 2.6.1
shakuhachi v0.4.0
Docfd: TUI multiline fuzzy document finder - 13.1.3 + proper user guide
OUPS meetup october 2026
faker 0.1.1: fake (but realistic) data, seed-compatible with faker-js
Old CWN
betacalendars 1.0.0 — deterministic date and calendar utilities
═══════════════════════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/ann-betacalendars-1-0-0-deterministic-date-and-calendar-utilities/18593/1>
Beta Calendars announced
────────────────────────
I’m happy to announce the first stable release of *betacalendars*, an
OCaml library for timezone-independent civil-date arithmetic and
deterministic calendar generation.
The library provides Gregorian date operations, configurable month and
year grids, bounded recurrence rules, and date-range and
calendar-boundary utilities. It is designed for predictable date-only
work without relying on local time zones.
Install it with opam:
┌────
│ opam update
│ opam install betacalendars
└────
• Source: <https://github.com/mateopedersen/betacalendars-ocaml>
• Release:
<https://github.com/mateopedersen/betacalendars-ocaml/releases/tag/v1.0.0>
• API docs: <https://mateopedersen.github.io/betacalendars-ocaml/>
• opam package metadata:
<https://github.com/ocaml/opam-repository/blob/master/packages/betacalendars/betacalendars.1.0.0/opam>
The package has been tested with OCaml 4.14 and 5.5, including its
test suite and generated documentation. Feedback and questions are
welcome.
Sedlex 3.8.1
════════════
Archive: <https://discuss.ocaml.org/t/ann-sedlex-3-8-1/18595/1>
Hhugo announced
───────────────
Sedlex 3.8.1 is out! 🎉
Sedlex is a unicode-friendly lexer generator for OCaml originally
written by Alain Frisch at LexiFi and now maintained under the
[ocaml-community] umbrella.
The headline feature is *named capture groups*. Sub-patterns can be
bound with OCaml's `as' syntax and read back in the action:
┌────
│ match%sedlex buf with
│ | (Plus ('0'..'9') as num), '.', (Plus ('0'..'9') as frac) ->
│ let n = Sedlexing.Utf8.of_submatch num in
│ let f = Sedlexing.Utf8.of_submatch frac in
│ Printf.printf "integer=%s fractional=%s\n" n f
│ | _ -> ()
└────
Captures are implemented with a tagged DFA, so the generated lexer
remains a single pass with no backtracking, and lexers that don't use
`as' generate the same code as before. Sub-matches are leftmost-greedy
within the longest match. `as' is not allowed under `Star', `Plus',
`Opt', `Rep', `Compl', `Sub' or `Intersect'.
This release also brings, among other things:
• Unicode 18.0.0
• Faster `lexeme', `sub_lexeme' and `of_submatch' for Latin1, UTF-8
and UTF-16
You can read the notes in
<https://github.com/ocaml-community/sedlex/releases/tag/v3.8>
(unreleased) and
<https://github.com/ocaml-community/sedlex/releases/tag/v3.8.1>.
It should be available soon on opam.
[ocaml-community] <https://github.com/ocaml-community>
opam 2.6.1
══════════
Archive: <https://discuss.ocaml.org/t/ann-opam-2-6-1/18597/1>
Kate announced
──────────────
Hi everyone,
*opam 2.6.1* is now available.
This release *fix*es a *regr*ession from 2.6.0 where `opam install
--deps-only' would *not inst*all the `depexts' field from the
*pack*ages being *reque*sted.
It also *impr*oves handling of Git repositories in things like
*docker* containers and works around a *bug* in Git-for-Windows
2.56.0.windows.1 (e.g. shipped by *GitHub Actions*)
:open_book: You can read our [blog post] for relevant *links* and
*details*.
[blog post] <https://opam.ocaml.org/blog/opam-2-6-1/>
Try it!
╌╌╌╌╌╌╌
The upgrade instructions are unchanged:
For Unix systems
┌────
│ bash -c "sh <(curl -fsSL https://opam.ocaml.org/install.sh) --version 2.6.1"
└────
or from PowerShell for Windows systems
┌────
│ Invoke-Expression "& { $(Invoke-RestMethod https://opam.ocaml.org/install.ps1) } -Version 2.6.1"
└────
Please report any issues to the [bug-tracker].
Happy hacking, <> <> The opam team <> <> :camel:
/Bold text is dotted around as an experiment to make it easier to read
and faster to comprehend/
[bug-tracker] <https://github.com/ocaml/opam/issues>
shakuhachi v0.4.0
═════════════════
Archive: <https://discuss.ocaml.org/t/ann-shakuhachi-v0-4-0/18599/1>
EruEri announced
────────────────
Dear all,
I’m happy to announce the release of shakuhachi v0.4.0.
Shakuhachi is still a music collection manager.
This release implements the 2 mains missing bits:
• Query float/date property from the command line
┌────
│ # example: List all musics of *Googgosh* played within the last 24 hour
│ $ skhc list %played_at:1dago..now %artist:Googoosh
│ # Or with the S-expression syntax
│ $ skhc list -Q "(and %played_at:1dago..now %artist:Googoosh)"
└────
• Complex stats are finally computed when querying an artist
┌────
│ # example: List all artists having at least two albums
│ $ skhc list -Iartist %album_count:2..
└────
This release also supports more… a sensible tagging/writing
properties.
• When adding a music the property /ALBUMARTISTS/ (resp. /ARTISTS/)
will be looked first and fallback to /*ALBUMARTIST/
(resp. /*ARTIST/).
• When tagging, two new options /-j/ and /-J/ which set a joinphrase
between the name of artists and artists of albums
┌────
│ $ skhc tag -a "Sona Jobarteh" -j '&' -a "Youssou N'Dour" Kambengwo.flac
│ # Will set ARTIST as a single value and ARTISTS as value containing two values
│ # ARTIST = Sona Jobarteh & Youssou N'Dour
│ # ARTISTS = Sona Jobarteh | Youssou N'Dour
└────
<https://codeberg.org/EruEri/shakuhachi>
Thanks you for your time Sincerely yours.
Docfd: TUI multiline fuzzy document finder - 13.1.3 + proper user guide
═══════════════════════════════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/ann-docfd-tui-multiline-fuzzy-document-finder-13-1-3-proper-user-guide/18601/1>
Darren announced
────────────────
Hi all,
I am happy to announce the release of Docfd 13.1.3. And since I got a
bit of time (got laid off from mass restructuring), I finally combined
all the scattered instructions into a proper (though basic) user
guide, which I hope nicely illustrates the cool parts of Docfd.
[User Guide] - [Repo]
[User Guide] <https://darrenldl.github.io/docfd/guide/index.html>
[Repo] <https://github.com/darrenldl/docfd>
What Docfd is
╌╌╌╌╌╌╌╌╌╌╌╌╌
Think interactive grep for text files, PDFs, DOCXs, etc, but
word/token based instead of regex and line based, so you can search
across lines easily.
Docfd aims to provide good UX via integration with common text editors
and PDF viewers, so you can jump directly to a search result with a
single key press.
<https://github.com/darrenldl/docfd/raw/main/demo-vhs-gifs/repo.gif>
Cheers, Darren
OUPS meetup october 2026
════════════════════════
Archive:
<https://discuss.ocaml.org/t/oups-meetup-november-2026/18610/1>
ancolie announced
─────────────────
The next OUPS meetup will take place on *Tuesday, 3rd of November*
2026. It will start at *6:30pm* at the *4 place Jussieu* in Paris. It
will be in the in the *amphitheater 45A*. There is a [map of the
buildings].
Please, *[register on meetup]* as soon as possible to let us know how
many pizza we should order.
For more details, you may check the [OUPS’ website ].
Moreover, we’d like to announce that the organizing team moved to the
[OCaml Zulip]. Feel free to contact us there if you’d like to suggest
talks.
—
This time we’ll have the following talks:
*Compiling FFI-heavy OCaml to WebAssembly: An Experience Report on
MOPSA – Réda Boudrouss*
Large OCaml applications often rely on native C and C++ libraries
through the OCaml FFI, making them difficult to run in the
browser. Existing browser backends compile OCaml to JavaScript or
WebAssembly, but leave the native dependency stack behind.
In this presentation, we explore a different approach: compiling the
OCaml runtime together with the complete native dependency stack to
WebAssembly using Emscripten, and running the original OCaml bytecode
on top of it. FFI calls are resolved through a static primitive table,
without modifying existing FFI code or CamlIDL-generated bindings.
We demonstrate this approach on MOPSA, a static analyzer combining
OCaml with LLVM/Clang, GMP, MPFR, Apron, and CamlIDL, and show how the
complete application can run directly in a web browser.
*Designing a Set-Theoretic Type Library in OCaml – Mickaël Laurent*
In this talk, I will share my experience using OCaml to design a
library for set-theoretic types. Set-theoretic types are difficult to
define because they consist of several recursive components and
layers. Furthermore, the termination of certain operations on
recursive types depends on a hash-consing system operating at various
levels. I will discuss the challenges and advantages of using OCaml,
such as the difficulty of making some recursive modules typecheck and
how we used algebraic effects to implement our hash-consing system.
—
After the talks there will be some pizzas offered by the [OCaml
Software Foundation] and later on we’ll move to a pub nearby as usual.
[map of the buildings]
<https://sciences.sorbonne-universite.fr/vie-de-campus-sciences/accueil-vie-pratique/plan-du-campus>
[register on meetup]
<https://www.meetup.com/fr-FR/ocaml-paris/events/316945503>
[OUPS’ website ] <https://oups.frama.io>
[OCaml Zulip] <https://ocaml.zulipchat.com>
[OCaml Software Foundation] <https://ocaml-sf.org>
faker 0.1.1: fake (but realistic) data, seed-compatible with faker-js
═════════════════════════════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/ann-faker-0-1-1-fake-but-realistic-data-seed-compatible-with-faker-js/18611/1>
Bartek Teodorczyk announced
───────────────────────────
I'm happy to announce [faker], a library for generating fake but
realistic data: names, addresses, emails, phone numbers, companies,
dates, finance data, lorem ipsum and more, in 77 locales.
┌────
│ opam install faker
└────
As far as I could find, OCaml didn't have a faker-style
library. Property-testing generators like QCheck give you random
values, but not plausible, localised fixtures for demos, seeding a
development database or snapshot tests.
faker is a port of [@faker-js/faker] 10.6.0, with **seed-for-seed
parity**: for the same seed, every method returns exactly what
faker-js returns. It uses the same MersenneTwister19937 generator and
the same algorithms, so an OCaml service and a JS/TS service can share
fixtures.
┌────
│ let () =
│ let f = Faker.create ~seed:42 () in
│ print_endline (Faker.Person.full_name f);
│ print_endline (Faker.Internet.email f);
│ print_endline (Faker.Location.city f);
│ print_endline
│ (Faker.Helpers.fake "{{person.firstName}} works as a {{person.jobTitle}}" f);
│ let de = Faker.Locales.De.faker () in
│ Faker.seed de 42;
│ print_endline (Faker.Person.full_name de);
│ let ja = Faker.Locales.Ja.faker () in
│ Faker.seed ja 42;
│ print_endline (Faker.Person.full_name ja)
└────
┌────
│ Nikita Crist
│ Moises.Sipes-Effertz18@gmail.com
│ Lolaville
│ Jeannette works as a Forward Implementation Analyst
│ Melinda Dragu
│ 吉川 結衣
└────
The equivalent faker-js code prints the same six lines.
*What's in it*
• All 26 faker-js modules (`Faker.Person', `Faker.Internet',
`Faker.Location', `Faker.Date', `Faker.Finance', `Faker.Commerce',
…) and all 77 locales.
• The API mirrors faker-js, so the [faker-js API reference] documents
every method. The faker instance is always the last argument, and
options are optional labelled arguments: `faker.number.int({ min: 1,
max: 10 })' becomes `Faker.Number.int ~min:1 ~max:10 f'.
• No dependencies beyond the stdlib and `unix'. Locales are linked on
demand, so an English-only program doesn't carry the other 76.
*How parity is checked*
`dune test' compares the OCaml output with fixtures generated by
running faker-js itself: 3 seeds for every case, plus a sweep of every
method in every locale (about 72,000 checks). Getting them all to pass
meant solving a few problems that may interest people here:
• *FMA contraction.* On arm64, the OCaml compiler fuses `a *. b +. c'
into a single fused multiply-add, which rounds differently from
V8. The port uses an explicit multiply where it matters.
• *Evaluation order.* OCaml evaluates function arguments and record
fields right to left, so every random draw is bound with `let' in
faker-js's order.
• *UTF-16 semantics.* JS string lengths, case mapping and NFKD
normalisation are emulated on UTF-8 strings, with tables generated
from Node.
• *Floating-point maths.* `location.nearbyGPSCoordinate' uses a port
of V8's fdlibm `sin~/~cos'. The one known platform dependence is
`Math.pow' in the exponential distributor: Node calls the system
libm, so faker-js itself rounds the last bit differently on
FreeBSD. opam-repo-ci found this, and 0.1.1 is the fix.
The porting notes are in [docs/PORTING.md], and the remaining
differences are listed in the [README] under "Known differences".
*Links*
• Package and API docs: <https://ocaml.org/p/faker>
• Source: <https://github.com/barteo/faker-ocaml>
• Issues: <https://github.com/barteo/faker-ocaml/issues>
All the data and algorithms come from faker-js, so many thanks to the
faker-js team and contributors. Feedback and bug reports are very
welcome, especially any case where the output differs from faker-js.
[faker] <https://ocaml.org/p/faker>
[@faker-js/faker] <https://github.com/faker-js/faker>
[faker-js API reference] <https://fakerjs.dev/api/>
[docs/PORTING.md]
<https://github.com/barteo/faker-ocaml/blob/main/docs/PORTING.md>
[README] <https://github.com/barteo/faker-ocaml#readme>
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 #1.1.2: Type: text/html, Size: 31127 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 568 bytes --]
next reply other threads:[~2026-10-13 6:58 UTC|newest]
Thread overview: 314+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 6:57 Alan Schmitt [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-06 13:15 Alan Schmitt
2026-09-29 7:10 Alan Schmitt
2026-09-22 7:41 Alan Schmitt
2026-09-15 8:08 Alan Schmitt
2026-09-08 13:20 Alan Schmitt
2026-09-01 9:14 Alan Schmitt
2026-08-25 7:36 Alan Schmitt
2026-08-18 6:56 Alan Schmitt
2026-08-11 12:25 Alan Schmitt
2026-08-04 7:44 Alan Schmitt
2026-07-28 12:44 Alan Schmitt
2026-07-21 16:02 Alan Schmitt
2026-07-14 7:16 Alan Schmitt
2026-07-07 13:29 Alan Schmitt
2026-06-30 13:25 Alan Schmitt
2026-06-23 10:07 Alan Schmitt
2026-06-16 10:51 Alan Schmitt
2026-06-09 7:39 Alan Schmitt
2026-06-02 9:01 Alan Schmitt
2026-05-26 7:36 Alan Schmitt
2026-05-19 8:52 Alan Schmitt
2026-05-12 7:28 Alan Schmitt
2026-05-05 9:35 Alan Schmitt
2026-04-28 7:59 Alan Schmitt
2026-04-21 9:34 Alan Schmitt
2026-04-14 9:50 Alan Schmitt
2026-04-07 9:32 Alan Schmitt
2026-03-31 6:10 Alan Schmitt
2026-03-24 9:58 Alan Schmitt
2026-03-17 14:39 Alan Schmitt
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=m24ieqf5p0.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