all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: 57253@debbugs.gnu.org, iyzsong@envs.net
Subject: [bug#57253] [PATCH 2/2] gnu: Add keychain.
Date: Wed, 21 Sep 2022 18:14:13 +0200	[thread overview]
Message-ID: <20220921181413.2a279512@alma-ubu.fritz.box> (raw)
In-Reply-To: <20220817000332.13801-1-GNUtoo@cyberdimension.org>

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

Hi Denis,
Hi iyzsong,

On Wed, 17 Aug 2022 02:03:32 +0200
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:

> * gnu/packages/crypto.scm (keychain): New variable.
> ---
>  gnu/packages/crypto.scm | 41
> +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41
> insertions(+)
> 
[..]
> +
> +(define-public keychain

In commit 3220edac2a5ac816328bd65489513ae8d33fbe23, you pushed the
first patch, but you missed this here, and the patchset is still open.

I cannot find any discussions about this.

Did you just miss pushing "keychain" patch, or was there a specific
reason why you hold it back?

Thanks,

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-09-21 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 23:46 [bug#57253] [PATCH 1/2] gnu: greybird-gtk-theme: Build with librsvg-for-system Denis 'GNUtoo' Carikli
2022-08-17  0:03 ` [bug#57253] [PATCH 2/2] gnu: Add keychain Denis 'GNUtoo' Carikli
2022-09-21 16:14   ` Björn Höfling [this message]
2022-09-21 21:52     ` Denis 'GNUtoo' Carikli
2022-09-22  8:00       ` bug#57253: " Björn Höfling
2022-08-17  5:38 ` [bug#57253] [PATCH 1/2] gnu: greybird-gtk-theme: Build with librsvg-for-system 宋文武 via Guix-patches via

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=20220921181413.2a279512@alma-ubu.fritz.box \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=57253@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.org \
    --cc=iyzsong@envs.net \
    /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.