From: Ricardo Wurmus <rekado@elephly.net>
To: Jonathan Frederickson <jonathan@terracrypt.net>
Cc: 36926-done@debbugs.gnu.org
Subject: bug#36926: [PATCH] gnu: Add libhandy.
Date: Mon, 05 Aug 2019 14:09:39 +0200 [thread overview]
Message-ID: <87pnljzud8.fsf@elephly.net> (raw)
In-Reply-To: <20190805001300.24655-1-jonathan@terracrypt.net>
Hi Jonathan,
thank you for this patch!
I applied a modified version of it with commit 213315d485 after these
changes:
* added a copyright line for you
* removed the “v” from the version field (and added it to the
git-reference instead)
* removed unneeded inputs
* moved some inputs to the native-inputs
* enabled tests (except for one)
* edited the description a little
Thanks again for your contribution!
--
Ricardo
prev parent reply other threads:[~2019-08-05 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 0:13 [bug#36926] [PATCH] gnu: Add libhandy Jonathan Frederickson
2019-08-05 12:09 ` Ricardo Wurmus [this message]
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=87pnljzud8.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36926-done@debbugs.gnu.org \
--cc=jonathan@terracrypt.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 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).