all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Charles <charles.b.jackson@protonmail.com>
Cc: 49345@debbugs.gnu.org
Subject: [bug#49345] Add CL-Hunchenissr-Routes and Its Dependencies
Date: Sat, 03 Jul 2021 12:39:20 +0000	[thread overview]
Message-ID: <87o8bjmv0n.fsf@kitej> (raw)
In-Reply-To: <GClskDkPBZ8tUWneiYv6Rq15VNHpVCc53cRs0w1yeoBwdZtKYcXBc4XQvuCgSw9N0dZp-Pr8rAk3JJOxoFdg8tI1OapmCLf1edqKW90qEXU=@protonmail.com>

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

Charles via Guix-patches via <guix-patches@gnu.org> skribis:

> Just let me know if this is to big of a change for an email or if anything else is wrong with it.

Having many patches attached to an email is not a problem. However all
your patches have the same "0001" prefix, it would be better if the
prefixes had the right number indicating in which order the patches must
be applied (although in this case it was not hard to find out).

I pushed cl-unification, cl-trivial-with-current-source-form, cl-tailrec
and cl-issr-core with a few modifications as
e2e17903fbb726467d74d8da367f51fa0206a12b and following.

However cl-hunchenissr requires the cl-portal package which is
apparently missing from your patches.

Could you send updated patches for cl-portal, cl-hunchenissr and
cl-hunchenissr-routes?

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

  reply	other threads:[~2021-07-03 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03  3:12 [bug#49345] Add CL-Hunchenissr-Routes and Its Dependencies Charles via Guix-patches via
2021-07-03 12:39 ` Guillaume Le Vaillant [this message]
2021-07-03 15:44   ` Charles via Guix-patches via
2021-07-05  8:14     ` bug#49345: " Guillaume Le Vaillant

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=87o8bjmv0n.fsf@kitej \
    --to=glv@posteo.net \
    --cc=49345@debbugs.gnu.org \
    --cc=charles.b.jackson@protonmail.com \
    /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.