From: Jake Leporte <jakeleporte@outlook.com>
To: 61018@debbugs.gnu.org
Cc: Jake Leporte <jakeleporte@outlook.com>
Subject: [bug#61018] [PATCH v6 0/2] Add pcsc-tools and dependency.
Date: Sun, 26 Feb 2023 18:42:33 -0600 [thread overview]
Message-ID: <MN2PR20MB260533C032E94C774F80B6EEACAF9@MN2PR20MB2605.namprd20.prod.outlook.com> (raw)
In-Reply-To: <MN2PR20MB26056405D5D05425ED070BC1ACC89@MN2PR20MB2605.namprd20.prod.outlook.com>
Re-submitting with proper commit messages, and hoping to get QA to succeed.
Jake Leporte (2):
gnu: Add perl-pcsc.
gnu: Add pcsc-tools.
gnu/packages/perl.scm | 36 +++++++++++++++++++
gnu/packages/security-token.scm | 62 +++++++++++++++++++++++++++++++++
2 files changed, 98 insertions(+)
base-commit: 81fbf5d71fb95367a0a93e45a86de5e930589a05
prerequisite-patch-id: 55ebfdbee35b36ac06da23b716337ecfef350452
prerequisite-patch-id: cc81d1d3eb9c0687793c8baf949901cd49c42650
prerequisite-patch-id: 52c97b6e4d8d4b78217423a3f1323d95a609de8c
prerequisite-patch-id: 90b350ab4778843697da28bb10344a84ccacc70c
--
2.39.1
next prev parent reply other threads:[~2023-02-27 0:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 4:29 [bug#61018] [PATCH 0/2] Add pcsc-tools, and missing dependency perl-pcsc Jake Leporte
2023-01-23 4:39 ` [bug#61018] [PATCH 1/2] gnu: Add perl-pcsc Jake Leporte
2023-01-23 4:40 ` [bug#61018] [PATCH 2/2] gnu: Add pcsc-tools Jake Leporte
2023-01-23 23:01 ` [bug#61018] [PATCH v2] gnu: Add perl-pcsc Jake Leporte
2023-01-27 2:26 ` [bug#61018] [PATCH v2] gnu: Add pcsc-tools Jake Leporte
2023-01-27 17:37 ` [bug#61018] [PATCH v3 1/2] gnu: Add perl-pcsc Jake Leporte
2023-01-28 2:57 ` [bug#61018] [PATCH v4] gnu: Add pcsc-tools Jake Leporte
2023-02-18 0:36 ` [bug#61018] [PATCH v5 1/2] gnu: Add perl-pcsc Jake Leporte
2023-02-27 0:42 ` Jake Leporte [this message]
2023-03-06 1:30 ` [bug#61018] [PATCH v7 " Jake Leporte
2023-03-22 1:40 ` [bug#61018] [PATCH 0/2] Add pcsc-tools, and missing dependency perl-pcsc Maxim Cournoyer
2023-03-22 1:50 ` bug#61018: " Maxim Cournoyer
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=MN2PR20MB260533C032E94C774F80B6EEACAF9@MN2PR20MB2605.namprd20.prod.outlook.com \
--to=jakeleporte@outlook.com \
--cc=61018@debbugs.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 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.