From: David Sterba <dsterba@suse.cz>
To: Alberto Bursi <alberto.bursi@outlook.it>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: dead links in wiki about why not using lz4
Date: Tue, 12 Sep 2017 13:58:00 +0200 [thread overview]
Message-ID: <20170912115800.GL14538@twin.jikos.cz> (raw)
In-Reply-To: <AM3PR08MB0642E6253ECA0099AEC6E06A92690@AM3PR08MB0642.eurprd08.prod.outlook.com>
On Tue, Sep 12, 2017 at 09:19:14AM +0000, Alberto Bursi wrote:
> Since zstd was added in btrfs there are people wondering why not lz4 too.
>
> The wiki paragraph [1] cites a couple dead links as explanations on why
> it's not a good idea to have lz4 in btrfs.
Regarding dead links, there's no replacement for the web interface of
gmane.org, so there are now many left.
prev parent reply other threads:[~2017-09-12 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 9:19 dead links in wiki about why not using lz4 Alberto Bursi
2017-09-12 9:33 ` Timofey Titovets
2017-09-12 11:55 ` David Sterba
2017-09-12 11:58 ` David Sterba [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170912115800.GL14538@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=alberto.bursi@outlook.it \
--cc=linux-btrfs@vger.kernel.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.
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 NNTP newsgroup(s).