From: Bruno Wolff III <bruno@wolff.to>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Lasse Collin <lasse.collin@tukaani.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Squashfs: add XZ compression support
Date: Tue, 21 Dec 2010 11:55:08 -0600 [thread overview]
Message-ID: <20101221175508.GA7180@wolff.to> (raw)
In-Reply-To: <4D0EF4FA.30703@lougher.demon.co.uk>
On Mon, Dec 20, 2010 at 06:17:30 +0000,
Phillip Lougher <phillip@lougher.demon.co.uk> wrote:
>
> As far as I'm concerned this makes a good point to make a new Squashfs tools
> release (very few people trust the CVS versions in my experience and always
> go for the last released version). I'll probably wait for a couple of weeks
> just in case CVS downloaders find any bugs (in practice I hardly ever get any
> bug reports from the CVS version). This means a Squashfs tools 4.2
> release mid January. How does this fit in with the release schedules for
> F15 and F16?
For the kernel stuff, I need to wait until it lands. This looks good for
making 2.6.38 which would make F15. If it doesn't then I'll continue to
wait. (Fedora is fairly strict on using upstream for kernel stuff except
where they have dedicated people as for video drivers.) (I may build
some personal kernels with the patches so I can test live images more
completely, but I can get by with testing squashfs-tools independently
for now.)
For squashfs-tools, a mid January release sounds plenty fine. It could slip
a lot and not cause a problem. I have some time off from work coming up next
week and will get a 4.2 prerelease (fromCVS) into rawhide next week so we can
get some testing there.
Thanks!
prev parent reply other threads:[~2010-12-21 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 6:05 Phillip Lougher
2010-12-10 18:52 ` Bruno Wolff III
2010-12-20 6:17 ` Phillip Lougher
2010-12-21 17:55 ` Bruno Wolff III [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=20101221175508.GA7180@wolff.to \
--to=bruno@wolff.to \
--cc=lasse.collin@tukaani.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.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
Powered by JetHome