From: ludo@gnu.org (Ludovic Courtès)
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 00/10] ocaml patches
Date: Wed, 08 Feb 2017 12:21:20 +0100 [thread overview]
Message-ID: <87lgthq66n.fsf@gnu.org> (raw)
In-Reply-To: <5664b4e3-b02d-b2be-96fc-3e9cd031460b@uq.edu.au> (Ben Woodcroft's message of "Wed, 8 Feb 2017 08:24:07 +1000")
Hi,
Ben Woodcroft <b.woodcroft@uq.edu.au> skribis:
> On 08/02/17 06:16, Julien Lepiller wrote:
>> On Tue, 31 Jan 2017 21:58:05 +0100
>> Julien Lepiller <julien@lepiller.eu> wrote:
>>
>>> Here is the next series of patches. I think I took into account all
>>> of your previous remarks, so it should be faster.
>>>
>>> Julien Lepiller (10):
>>> gnu: Add ocaml-fieldslib.
>>> gnu: Add ocaml-ppx-core.
>>> gnu: Add ocaml-ppx-optcomp.
>>> gnu: Add ocaml-ppx-driver.
>>> gnu: Add ocaml-cppo.
>>> gnu: Add ocaml-ppx-deriving.
>>> gnu: Add ocaml-ppx-type-conv.
>>> gnu: Add ocaml-ppx-inline-test.
>>> gnu: Add ocaml-ppx-bench.
>>> gnu: Add ocaml-ppx-compare.
>>>
>>> gnu/packages/ocaml.scm | 255
>>> +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 255
>>> insertions(+)
>>>
>> Up?
>>
>> Can I push them?
> I've been meaning to review these patches but haven't found the time..
>
> If they pass 'guix lint' then I would think it is OK to push
> them. Thanks for your efforts on the OCaml front.
I concur, sorry for the delay Julien!
That’s really a minor issue but in the future, please make sure
descriptions contain full sentences and use @code and similar where it
makes sense.
Also, feel free to push simple packages if they pass ‘guix lint’ and you
don’t get feedback within a few days (see ‘HACKING’).
Thanks for working the OCaml front! :-)
Ludo’.
next prev parent reply other threads:[~2017-02-08 11:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 20:58 [PATCH 00/10] ocaml patches Julien Lepiller
2017-01-31 20:58 ` [PATCH 01/10] gnu: Add ocaml-fieldslib Julien Lepiller
2017-01-31 20:58 ` [PATCH 02/10] gnu: Add ocaml-ppx-core Julien Lepiller
2017-01-31 20:58 ` [PATCH 03/10] gnu: Add ocaml-ppx-optcomp Julien Lepiller
2017-01-31 20:58 ` [PATCH 04/10] gnu: Add ocaml-ppx-driver Julien Lepiller
2017-02-08 11:17 ` Ludovic Courtès
2017-02-13 21:22 ` Julien Lepiller
2017-02-14 9:12 ` Ludovic Courtès
2017-01-31 20:58 ` [PATCH 05/10] gnu: Add ocaml-cppo Julien Lepiller
2017-01-31 20:58 ` [PATCH 06/10] gnu: Add ocaml-ppx-deriving Julien Lepiller
2017-01-31 20:58 ` [PATCH 07/10] gnu: Add ocaml-ppx-type-conv Julien Lepiller
2017-01-31 20:58 ` [PATCH 08/10] gnu: Add ocaml-ppx-inline-test Julien Lepiller
2017-01-31 20:58 ` [PATCH 09/10] gnu: Add ocaml-ppx-bench Julien Lepiller
2017-01-31 20:58 ` [PATCH 10/10] gnu: Add ocaml-ppx-compare Julien Lepiller
2017-02-07 20:16 ` [PATCH 00/10] ocaml patches Julien Lepiller
2017-02-07 22:24 ` Ben Woodcroft
2017-02-08 11:21 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-18 20:27 Julien Lepiller
2017-01-18 22:27 ` Marius Bakke
2017-01-19 8:56 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgthq66n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=b.woodcroft@uq.edu.au \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).