From: Marius Bakke <mbakke@fastmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>, 27814@debbugs.gnu.org
Subject: [bug#27814] [PATCH] gnu: Add lziprecover.
Date: Tue, 25 Jul 2017 23:19:36 +0200 [thread overview]
Message-ID: <87y3rccizb.fsf@fastmail.com> (raw)
In-Reply-To: <20170725031443.17909-1-me@tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 127 bytes --]
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> * gnu/packages/compression.scm (lziprecover): New variable.
Looks good to me!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-07-25 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 3:14 [bug#27814] [PATCH] gnu: Add lziprecover Tobias Geerinckx-Rice
2017-07-25 21:19 ` Marius Bakke [this message]
2017-07-26 17:41 ` bug#27814: " Tobias Geerinckx-Rice
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=87y3rccizb.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=27814@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).