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, 20 Aug 2024 11:29:49 +0200 [thread overview]
Message-ID: <m2jzgbbkz6.fsf@mac-03220211.irisa.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 15128 bytes --]
Hello
Here is the latest OCaml Weekly News, for the week of August 13 to 20,
2024.
Table of Contents
─────────────────
MlFront - A Java-like package system for OCaml
Rpmfile library v0.3.0 with new Eio-based reader
GitHub - meta-introspector/ocaml-libppx-import-yojson-introspector: Using libppx, ppx_import, reflect over ast using
Dune Developer Preview Updates
Ppxlib dev meetings
Pragmatic Category Theory: Part 2 published!
Dune dev meeting on 2024-08-21, 10am CEST
Other OCaml News
Old CWN
MlFront - A Java-like package system for OCaml
══════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/ann-mlfront-a-java-like-package-system-for-ocaml/15072/8>
jbeckford announced
───────────────────
There is now a new library `MlFront_Top' with a build tool
`mlfront-top' that will generate self-contained OCaml toplevel script
files with parallelism based on @c-cube's moonpool library:
┌────
│ .
│ ├── AcmeWidgets_Std/
│ │ ├── JobsA1.ml
│ │ └── JobsA2.ml
│ └── BobBuilder_Std/
│ └── JobsB.ml
└────
┌────
│ $ mlfront-top -o buildscript.ml
│
│ $ ocaml buildscript.ml -j 2 -native
│ legend: -> start | <- finish
│ directory create: target/
│ file create: target/AcmeWidgets_Std.ml
│ link create: AcmeWidgets_Std/JobsA1.ml -> target/AcmeWidgets_Std__JobsA1.ml
│ link create: AcmeWidgets_Std/JobsA2.ml -> target/AcmeWidgets_Std__JobsA2.ml
│ link create: BobBuilder_Std/JobsB.ml -> target/BobBuilder_Std__JobsB.ml
│ -> compile: AcmeWidgets_Std.JobsA1
│ -> compile: AcmeWidgets_Std.JobsA2
│ <- compile: AcmeWidgets_Std.JobsA1
│ <- compile: AcmeWidgets_Std.JobsA2
│ -> compile: AcmeWidgets_Std
│ <- compile: AcmeWidgets_Std
│ -> compile: BobBuilder_Std.JobsB
│ <- compile: BobBuilder_Std.JobsB
│ -> executable create: BobBuilder_Std.JobsB
│ <- executable create: BobBuilder_Std.JobsB
│ done.
│
│ $ target/BobBuilder_Std.JobsB
│ I am an A1!
│ I am an A2!
│ I am a B!
└────
It requires the `ocaml' binary and `ocamlc' or `ocamlopt'. The
complete example is at
<https://gitlab.com/dkml/build-tools/MlFront/-/blob/0.4.0-6/tests/MlFront_Top/jobs.t/run.t>.
Rpmfile library v0.3.0 with new Eio-based reader
════════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/rpmfile-library-v0-3-0-with-new-eio-based-reader/15149/1>
Mikhail announced
─────────────────
Today I want to tell you about new version of [Rpmfile
library]. Rpmfile is a library for reading metadata from [RPM]
packages. Originally Rpmfile's parser (reader) used [Angstrom] for
parsing. And in the new release added new modern [Eio]-based reader.
Globally, the project is now split into four packages: `rpmfile',
which contains signatures and implementation-independent functions,
`rpmfile-unix' with the original Angstrom parser, and `rpmfile-eio'
(with `rpmfile-cli') written using Eio.
[Rpmfile library] <https://github.com/dx3mod/rpmfile>
[RPM] <https://en.wikipedia.org/wiki/RPM_Package_Manager>
[Angstrom] <https://github.com/inhabitedtype/angstrom>
[Eio] <https://github.com/ocaml-multicore/eio>
My experience porting to Eio
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
Eio is a fantastic effect-based I/O library for a more modern age in
multicore OCaml. I think it takes the best ideas from the
ecosystem. So built-in `Buf_read' and `Buf_write' modules implement
ideas from Angstrom and Faraday libraries. Almost API one-to-one,
allowing porting via copy-paste.
But, of course, not everything is so perfect. Unlike the
`Angstrom.parse_' function, the `Buf_read.parse' function thinks I
want to read a whole stream to end of input.
A snippet of the source code:
┌────
│ let parse ?initial_size ~max_size p flow =
│ let buf = of_flow flow ?initial_size ~max_size in
│ format_errors (p <* end_of_input) buf
│ (* ^^^^^^^^^^^^^^^
│ 0_0 nice (not) *)
└────
So I had to rewrite this function myself in a form similar to
`Angstrom.Consume.Prefix'.
◊ Is it a signed or unsigned integer?
`BE.uint16' and other similar functions are *signed int* even though
they have the prefix `u' in the name for some reason.
◊ And a few other differences
• `Angstrom.advance' is `skip'
• `Angstrom.pos' is `consumed_bytes'
P.S.
╌╌╌╌
Thanks for your attention!
GitHub - meta-introspector/ocaml-libppx-import-yojson-introspector: Using libppx, ppx_import, reflect over ast using
════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/github-meta-introspector-ocaml-libppx-import-yojson-introspector-using-libppx-ppx-import-reflect-over-ast-using/15151/1>
Jim Dupont announced
────────────────────
Here is a working first version (with warts) of a ppxlib to yojson
converter, am still testing it but the hello world is working, I have
tried multiple times to get this to work, and finally settled on the
import route to override the type system. code here:
<https://github.com/meta-introspector/ocaml-libppx-import-yojson-introspector>
example snippet
┌────
│ {
│ "pexp_desc": [
│ "Pexp_constant",
│ [
│ "Pconst_string",
│ "Hello, World!"
│ ]
│ ]
│ }
└────
Dune Developer Preview Updates
══════════════════════════════
Archive:
<https://discuss.ocaml.org/t/ann-dune-developer-preview-updates/15160/1>
ostera announced
────────────────
Just wanted to share some of the work the Dune has been up to lately
re: the Developer Preview we announced [here] :) – we'll be using this
thread to share more updates as things go.
As always, we hold our Dune Developer meetings in public and you're
more than welcome to subscribe to our public Calendar ([Google],
[iCal])
[here]
<https://discuss.ocaml.org/t/ocaml-platform-newsletter-march-may-2024/14765>
[Google]
<https://calendar.google.com/calendar/embed?src=c_5cd698df6784e385b1cdcdc1dbca18c061faa96959a04781566d304dc9ec7319%40group.calendar.google.com&ctz=Europe%2FStockholm>
[iCal]
<https://calendar.google.com/calendar/ical/c_5cd698df6784e385b1cdcdc1dbca18c061faa96959a04781566d304dc9ec7319%40group.calendar.google.com/public/basic.ics>
Getting ready for the Public Beta
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
As we prepare for the public beta, we're ramping up the DX interviews
and ensuring the first few users will have a fun, productive
experience with the developer preview.
:inbox_tray: If you signed up for the Dev Preview back in
May, check your inbox for a link and instructions to
schedule your DX interview with us.
Here's a sample video ([Mastodon] or [X]) where you can see me
building the Riot project on a machine that does not have OCaml
installed. It is pretty neat!
Seriously, big shoutout to the Dune team at Tarides[0] who have been
doing a phenomenal job :clap: :sparkles: :camel:
So here's what getting started with OCaml looks like today with the
Dune Developer Preview as of today (August 19 2024):
1. get `dune' from our binary distribution – we'll soon make this
public!
2. run `dune pkg lock' in your favorite project
3. run `dune build'
That's it. No need to install anything else, Dune will see that lock
file, fetch, and build all necessary dependencies.
:world_map: These are some strong step towards the [OCaml
Platform vision for 2026], that we are actively working
towards. If you have any thoughts or feedback please let
me know!
There are more improvements coming that will help remove friction to
get started and creating a delightful experience. Both of these things
we strongly believe will help onboard new users to the OCaml world.
Here's a few in the works:
• *Various DX improvements* – from new outputs to simplified
workflows, we want to make using Dune just delightful.
• *Bundled support for dev tools* (ocalmformat, odoc, lsp) – the
default toolset will be available without any extra steps! just
call `dune fmt', and it works. No need to manually install anything
else.
• *Automatic dependency locking* – when building, and even on watch
mode, Dune will lock your dependencies by default and keep the lock
up to date.
• *Cross-project Caching* – by default we'll enabled a local Dune
cache that across the system, so you never rebuild the same
dependency even across projects.
• *Signed binaries with certificates of origin* – we care deeply about
security and want to make sure that any binary we ship will be
easily verified and tracked back to its sources.
Stay tuned! :wave:
PS: here's a longer video ([Mastodon], [X]) showing you the setup for
OCaml from zero, creating a new project, and adding a dependency, all
within ~5 minutes
[0] @emillon @Leonidas @gridbugs @tmattio. Ambre Shumay, Alpha Diallo,
Etienne Marais
[Mastodon] <https://mas.to/deck/@leostera/112988841207690720>
[X] <https://x.com/leostera/status/1825519465527673238>
[OCaml Platform vision for 2026]
<https://ocaml.org/tools/platform-roadmap>
[Mastodon] <https://mas.to/deck/@leostera/112988880290815356>
[X] <https://x.com/leostera/status/1825519469759812062>
Ppxlib dev meetings
═══════════════════
Archive: <https://discuss.ocaml.org/t/ppxlib-dev-meetings/12441/29>
Nathan Rebours announced
────────────────────────
This month's meeting is scheduled for tomorrow, [date=2024-08-20
time=17:00:00 timezone="Europe/London"]!
The meeting agenda thus far is to discuss the following:
• *5.2 Bump Progess*
• Auto-generate AST pattern code and labelled arguments
(e.g. `value_binding ~constraint_:none' but no positional
argument?)
• `Ast_helper.Exp.function_' deprecation
• [opam-repository overlay for 5.2 AST bump]
• *Issues in migrations*
• Bumping the AST has uncovered issues in migrating code up and down
the internal ppxlib ASTs – would be good to discuss this and also
how to mitigate this going forward.
• *Documentation*
• Great user feedback from [Ppxlib: Getting the original definition
of `typ_constr' like `type_declaration' from `core_type' of
`ptyp_constr'] which we should take onboard and work into
<https://github.com/ocaml-ppx/ppxlib/issues/324>
• *Some carry over items from last month*
• In general what is the medium term goals for ppxlib? Mostly
maintenance and bumping the AST/keeping up with compiler releases?
The meeting will be hosted on google meet here:
<https://meet.google.com/yxw-ejnu-cju>
Everyone is very welcome to join! :camel:
[opam-repository overlay for 5.2 AST bump]
<https://github.com/patricoferris/opam-ppxlib-repository>
[Ppxlib: Getting the original definition of `typ_constr' like
`type_declaration' from `core_type' of `ptyp_constr']
<https://discuss.ocaml.org/t/ppxlib-getting-the-original-definition-of-typ-constr-like-type-declaration-from-core-type-of-ptyp-constr/15110>
Pragmatic Category Theory: Part 2 published!
════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/new-part-pragmatic-category-theory-part-2-published/15056/6>
Dmitrii Kovanikov announced
───────────────────────────
I just published [the second part] of my series, so I updated the
topic.
Let me know when notifications become too noisy :slight_smile:
[the second part]
<https://dev.to/chshersh/pragmatic-category-theory-part-2-composing-semigroups-87>
Dune dev meeting on 2024-08-21, 10am CEST
═════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/ann-dune-dev-meeting-on-2024-08-21-10am-cest/15166/1>
Steve Sherratt announced
────────────────────────
Hi! The next public dune dev meeting will be held on 2024-08-21, 10am
CEST. Please feel free to let me know any topics you'd like us to
discuss and I'll update [the meeting notes]. The zoom link for the
meeting is:
<https://us06web.zoom.us/j/85096877776?pwd=cWNhU1dHQ1ZNSjZuOUZCQ0h2by9Udz09>
[the meeting notes]
<https://github.com/ocaml/dune/wiki/dev-meeting-2024-08-21>
Other OCaml News
════════════════
From the ocaml.org blog
───────────────────────
Here are links from many OCaml blogs aggregated at [the ocaml.org
blog].
• [The new Tar release, a retrospective]
[the ocaml.org blog] <https://ocaml.org/blog/>
[The new Tar release, a retrospective]
<https://blog.robur.coop/articles/tar-release.html>
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: 27121 bytes --]
next reply other threads:[~2024-08-20 9:29 UTC|newest]
Thread overview: 236+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 9:29 Alan Schmitt [this message]
-- strict thread matches above, loose matches on Subject: below --
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-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=m2jzgbbkz6.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