all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: <florhizome@posteo.net>, <60013@debbugs.gnu.org>
Subject: [bug#60013] [PATCH 1/3] gnu: Add libmodule
Date: Mon, 12 Dec 2022 21:00:42 +0000	[thread overview]
Message-ID: <CP0547KC2GSW.REG9A8KPX713@guix-framework> (raw)
In-Reply-To: <91575b0f95b5a71b18108b57fa1a366e0f6044c9.1670876889.git.florhizome@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

Heya,

On Mon Dec 12, 2022 at 8:31 PM GMT,  wrote:
> zimoun: yes I usually send an empty mail before a patchset wit multiple patches

There's a better way, using ``--cover-letter'':
<https://guix.gnu.org/manual/devel/en/html_node/Sending-a-Patch-Series.html#Multiple-Patches-1>

* gnu/packages/wm.scm (libmodule): New variable.

--- a/gnu/packages/c.scm
+++ b/gnu/packages/c.scm

@@ -1300,6 +1300,28 @@ (define-public libdispatch

+       (uri (git-reference
+             (url "https://github.com/FedeDP/libmodule")
+             (commit version)))

Please add a ``file-name'':

  (file-name (git-file-name name version))

+    (arguments '(#:tests? #f)) ;tests not found

Use ``list'':

  (list #:tests? #f)

+    (description "Libmodule offers a small and simple C implementation of an
+ actor library that aims to let developers easily create modular C projects.")

There should be indentation between ``description'' and ``"..."''; also, some of
it seems a wee bit markety.  How about this?

  (description
   "Libmodule provides a C implementation of the actor model, aiming to help
  with the creation of modular C projects.")

    -- (

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2022-12-12 21:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 16:53 [bug#60013] [PATCH] gnu: Add clight Florian
2022-12-12 19:16 ` zimoun
2022-12-12 20:51   ` Tobias Geerinckx-Rice via Guix-patches via
2022-12-12 20:31 ` [bug#60013] [PATCH 1/3] gnu: Add libmodule florhizome
2022-12-12 20:31   ` [bug#60013] [PATCH 2/3] gnu: Add clightd florhizome
2022-12-12 21:53     ` ( via Guix-patches via
2022-12-12 20:31   ` [bug#60013] [PATCH 3/3] gnu: Add clight florhizome
2022-12-12 21:57     ` ( via Guix-patches via
2022-12-12 21:00   ` ( via Guix-patches via [this message]
2022-12-12 23:48   ` [bug#60013] [PATCH 1/3] gnu: Add libmodule zimoun
2022-12-13 11:51     ` Florian
2022-12-15 11:31       ` zimoun
2022-12-20 16:33         ` Florian
2022-12-21 11:22           ` ( via Guix-patches via
2022-12-30 12:45           ` zimoun

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=CP0547KC2GSW.REG9A8KPX713@guix-framework \
    --to=guix-patches@gnu.org \
    --cc=60013@debbugs.gnu.org \
    --cc=florhizome@posteo.net \
    --cc=paren@disroot.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 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.