Lucas Pluvinage

Indeed we don't need the `.git` directory. I couldn't find any documentation for the `--work-tree` argument in `git checkout`, instead I'm reading about [git worktree](https://git-scm.com/docs/git-worktree): is it what you are...

> On that basis, perhaps deprecating the argument's optional nature is the better route to go - possibly with the call in #248 exposed as an API function so that...

Looking at the implementation it's indeed equivalent, thanks for the pointer. But yes labelling the cancellation context remains useful.

Custom event rings PR: https://github.com/ocaml/ocaml/pull/11474 We should make sure that it fits Eio's requirements.

The new version of `bigarray-compat` should fix the issue: https://github.com/ocaml/opam-repository/pull/20553

Regarding mirage compatibility, I've done some experiments and it's possible to separate the nocrypto core and mirage packages in several repositories. I've done the modifications here: * https://github.com/TheLortex/ocaml-nocrypto/tree/dune-separate-mirage contains the...

I definitely agree with you, this was to show that it's _possible_ but definitely not good looking. > Is it not possible to simply add build flags for particular tools...

So it looks like we're going with what you suggested, and therefore it should be good for `nocrypto` to switch to dune. However we need some changes to get it...

Well the problem is that `tls` is full of sexp derivers and we can't totally remove them as it's part of the public API (to pass client/server configuration). So this...

Currently you have to use `-f mirage/config.ml` everywhere, which I agree is not very practical. > Also, in the generated Makefile (at top level) the build target omits the -f...