From: ludo@gnu.org (Ludovic Courtès)
To: Julien Lepiller <julien@lepiller.eu>
Cc: 33437@debbugs.gnu.org
Subject: [bug#33437] [PATCH 10/10] gnu: ocaml-lambda-term: Use dune-build-system.
Date: Sat, 24 Nov 2018 22:18:27 +0100 [thread overview]
Message-ID: <87ftvqyy1o.fsf@gnu.org> (raw)
In-Reply-To: <20181119222821.16789-10-julien@lepiller.eu> (Julien Lepiller's message of "Mon, 19 Nov 2018 23:28:21 +0100")
The remaining patches LGTM. Perhaps it would be best to commit all this
to ‘core-updates’, to avoid gratuitous rebuilds of all the OCaml
packages now that we’re close to merging ‘core-updates’.
Thank you!
Ludo’.
next prev parent reply other threads:[~2018-11-24 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 22:25 [bug#33437] [PATCH] Add dune-build-system Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 01/10] build: " Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 02/10] gnu: ocaml-migrate-parsetree: Use dune-build-system Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 03/10] gnu: ocaml-ppx-tools-versioned: " Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 04/10] gnu: ocaml-bitstring: " Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 05/10] gnu: ocaml-lwt: " Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 06/10] gnu: ocaml-lwt-log: " Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 07/10] gnu: ocaml-cppo: " Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 08/10] gnu: ocaml-re: " Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 09/10] gnu: ocaml-camomile: " Julien Lepiller
2018-11-19 22:28 ` [bug#33437] [PATCH 10/10] gnu: ocaml-lambda-term: " Julien Lepiller
2018-11-24 21:18 ` Ludovic Courtès [this message]
2018-11-24 21:17 ` [bug#33437] [PATCH 01/10] build: Add dune-build-system Ludovic Courtès
2018-12-18 21:41 ` bug#33437: [PATCH] " Julien Lepiller
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=87ftvqyy1o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33437@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.