From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Cairn" <cairn@pm.me>, <57326@debbugs.gnu.org>
Subject: [bug#57326] [PATCH 5/7] gnu: Add go-github-com-emersion-go-vcard.
Date: Sun, 28 Aug 2022 08:52:22 +0100 [thread overview]
Message-ID: <CMHHYV9K74L0.ZZ27FB0TO5OX@guix-aspire> (raw)
In-Reply-To: <20220821234352.16268-1-cairn@pm.me>
On Mon Aug 22, 2022 at 12:43 AM BST, Cairn via Guix-patches via wrote:
> + (arguments
> + `(#:import-path "github.com/emersion/go-vcard"))
Again, list style.
> + (inputs (list))
No need for this field.
> + (home-page "https://github.com/emersion/go-vcard")
> + (synopsis "Go library for the vCard file format")
> + (description "This package lets you parse and format vCard in Go.")
Description formatting here, too. Also, IMO "parse and format vCard" sounds
a little weird.
-- (
next prev parent reply other threads:[~2022-08-28 8:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 19:33 [bug#57326] [PATCH 0/7] gnu: Add hydroxide Cairn via Guix-patches via
2022-08-21 23:42 ` [bug#57326] [PATCH 1/7] gnu: go-github-com-emersion-go-imap: Update to 1.2.1 Cairn via Guix-patches via
2022-08-28 7:41 ` ( via Guix-patches via
2022-08-21 23:42 ` [bug#57326] [PATCH 2/7] gnu: Add go-github-com-boltdb-bolt Cairn via Guix-patches via
2022-08-28 7:44 ` ( via Guix-patches via
2022-08-21 23:43 ` [bug#57326] [PATCH 3/7] gnu: Add go-github-com-emersion-go-bcrypt Cairn via Guix-patches via
2022-08-28 7:47 ` ( via Guix-patches via
2022-08-21 23:43 ` [bug#57326] [PATCH 4/7] gnu: Add go-github-com-emersion-go-mbox Cairn via Guix-patches via
2022-08-28 7:51 ` ( via Guix-patches via
2022-08-21 23:43 ` [bug#57326] [PATCH 5/7] gnu: Add go-github-com-emersion-go-vcard Cairn via Guix-patches via
2022-08-28 7:52 ` ( via Guix-patches via [this message]
2022-08-21 23:44 ` [bug#57326] [PATCH 6/7] gnu: Add go-github-com-emersion-go-webdav Cairn via Guix-patches via
2022-08-28 7:53 ` ( via Guix-patches via
2022-08-21 23:44 ` [bug#57326] [PATCH 7/7] gnu: Add hydroxide Cairn via Guix-patches via
2022-08-28 7:56 ` ( via Guix-patches via
2022-08-28 7:59 ` ( via Guix-patches via
2022-08-29 0:23 ` [bug#57326] [PATCH 0/7] " Cairn via Guix-patches via
2022-09-08 14:18 ` Olivier Dion via Guix-patches via
2022-09-10 9:39 ` Cairn via Guix-patches via
2022-09-10 7:51 ` ( via Guix-patches via
2022-09-10 9:32 ` Cairn via Guix-patches via
2022-08-28 1:05 ` Olivier Dion via Guix-patches via
2022-08-28 1:13 ` Cairn via Guix-patches via
2022-10-14 23:04 ` [bug#57326] Delays Cairn via Guix-patches via
2022-11-27 16:31 ` [bug#57326] (No Subject) Tyler Wolf via Guix-patches via
2022-11-27 16:36 ` ( via Guix-patches via
2023-01-06 19:49 ` Olivier Dion 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
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=CMHHYV9K74L0.ZZ27FB0TO5OX@guix-aspire \
--to=guix-patches@gnu.org \
--cc=57326@debbugs.gnu.org \
--cc=cairn@pm.me \
--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 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).