linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Phillip Lougher <phillip.lougher@gmail.com>
Cc: Phillip Lougher <phillip@squashfs.org.uk>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] Squashfs: add LZ4 compression
Date: Tue, 23 Jul 2013 11:29:13 -0500	[thread overview]
Message-ID: <20130723162913.GA25886@wolff.to> (raw)
In-Reply-To: <CAB3wodfLzHMS1b3kQXKYvmWLLoYOhenwmMfS-cSU3w1gLFCh-g@mail.gmail.com>

On Tue, Jul 23, 2013 at 17:17:30 +0100,
   Phillip Lougher <phillip.lougher@gmail.com> wrote:
>
>In otherwords I don't think it's wise yet to merge LZ4 onto stable,
>not until at least there's some positive feedback on the mailing list.
>
>Thoughts?  Maybe some positive feedback? :-)

I think it makes sense to tie inclusion in the kernel with inclusion 
into the stable branch. If this gets into the 3.11 kernel, I'm going 
to want to get it into Fedora releases that use that kernel. This 
will initially be Fedora 20 (which will branch from rawhide in a couple 
of weeks) and will eventually be in Fedora 19 and probably Fedora 18. 
So I'd like to see it in stable, since I would feel less comfortable 
using the master branch.

If LZ4 support isn't in the kernel I think that there isn't a lot of 
need for support in Fedora since I don't think many people use it 
for archiving. It mostly gets used for live images. I'll make sure 
that LZ4 can be used for them, but I suspect most people will still 
prefer xz for them. But probably at least some people would prefer 
faster decompression rather than minimal size. As flash drives get 
bigger (for the same cost) more people will probably prefer speed over 
size.

  reply	other threads:[~2013-07-23 16:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  2:21 [PATCH 0/2] Squashfs: add LZ4 compression Phillip Lougher
2013-07-22  2:21 ` [PATCH 1/2] Squashfs: add LZ4 compression support Phillip Lougher
2013-07-22  4:35   ` Joe Perches
2013-07-22  2:21 ` [PATCH 2/2] Squashfs: Add LZ4 compression configuration option Phillip Lougher
2013-07-22  3:05 ` [PATCH 0/2] Squashfs: add LZ4 compression Gu Zheng
2013-07-22  5:07   ` Phillip Lougher
2013-07-22  6:04     ` Gu Zheng
2013-07-22 13:38       ` Phillip Lougher
2013-07-26 22:00       ` Rob Landley
2014-09-05 10:01       ` Guan, Xin
2014-09-06 20:29       ` Guan, Xin
     [not found] ` <20130723151009.GA5971@wolff.to>
2013-07-23 16:17   ` Phillip Lougher
2013-07-23 16:29     ` Bruno Wolff III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-27  8:00 Phillip Lougher
2014-11-27 13:37 ` Bruno Wolff III
     [not found]   ` <CAJZww4gzTnbyB4jbFQc0N4G6GJ31pVwv-PNZtDMbUxXMoH-orQ@mail.gmail.com>
2014-11-27 16:55     ` Martin Vath
2014-12-12  7:44 ` Dave Vasilevsky
2014-12-12  8:31   ` Anthony F McInerney
2014-12-12 10:27 ` Guan Xin
     [not found] ` <CAGw_SrN6tZyXRx6pxkpnhWc2U5845HRbfzhOK5v9qkjWejFpmA@mail.gmail.com>
2014-12-12 15:56   ` Bruno Wolff III
2014-12-12 22:45     ` Phillip Lougher

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=20130723162913.GA25886@wolff.to \
    --to=bruno@wolff.to \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillip.lougher@gmail.com \
    --cc=phillip@squashfs.org.uk \
    /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).