From: "Ludovic Courtès" <ludo@gnu.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 45460@debbugs.gnu.org
Subject: [bug#45460] [PATCH 3/5] publish: Add support for zstd compression.
Date: Sun, 03 Jan 2021 16:18:30 +0100 [thread overview]
Message-ID: <87turyyrp5.fsf@gnu.org> (raw)
In-Reply-To: <0ccd6512-566f-3c5a-cd62-65a2d320d919@web.de> (Jonathan Brielmaier's message of "Mon, 28 Dec 2020 10:17:50 +0100")
Hallo!
Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:
> Nice thing, only one nitpick
[...]
>> +The compression ratio of @code{zstd} is between that of @code{lzip} and
>> +that of @code{gzip}; its main advantage is a
>> +@uref{https://facebook.github.io/zstd/,high decompression speed}.
>>
>> Unless @option{--cache} is used, compression occurs on the fly and
>> the compressed streams are not
>
> It should be also documented at the `guix-publish-configuration` section
> in the manual. As I guess that a lot of publish server admins look there...
Good point, I’ll add a cross-reference there.
Ludo’.
next prev parent reply other threads:[~2021-01-03 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 14:13 [bug#45460] [PATCH 0/5] Zstd support for 'guix publish' and 'guix substitute' Ludovic Courtès
2020-12-27 14:38 ` [bug#45460] [PATCH 1/5] utils: Remove 'compressed-output-port' Ludovic Courtès
2020-12-27 14:38 ` [bug#45460] [PATCH 2/5] utils: Support zstd compression via Guile-zstd Ludovic Courtès
2020-12-27 14:38 ` [bug#45460] [PATCH 3/5] publish: Add support for zstd compression Ludovic Courtès
2020-12-28 9:17 ` Jonathan Brielmaier
2021-01-03 15:18 ` Ludovic Courtès [this message]
2020-12-27 14:38 ` [bug#45460] [PATCH 4/5] substitute: Add zstd support Ludovic Courtès
2020-12-27 14:38 ` [bug#45460] [PATCH 5/5] doc: Mention optional dependency on Guile-zstd Ludovic Courtès
2020-12-30 9:30 ` [bug#45460] [PATCH 0/5] Zstd support for 'guix publish' and 'guix substitute' Mathieu Othacehe
2021-01-03 15:17 ` Ludovic Courtès
2021-01-13 22:08 ` Ludovic Courtès
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=87turyyrp5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=45460@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.de \
/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).