All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: linux-kernel@vger.kernel.org,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [Announce] Squashfs 2.1 released (compressed filesystem)
Date: Sat, 11 Dec 2004 07:39:22 -0800	[thread overview]
Message-ID: <20041211153922.GA29523@kroah.com> (raw)
In-Reply-To: <41BA825F.9040509@lougher.demon.co.uk>

On Sat, Dec 11, 2004 at 05:15:11AM +0000, Phillip Lougher wrote:
> Greg KH wrote:
> >On Fri, Dec 10, 2004 at 08:08:37PM +0000, Phillip Lougher wrote:
> >
> >>I'm pleased to announce the release of Squashfs 2.1.
> >
> >
> >Are you going to submit this fs for inclusion in the main kernel tree?
> >I'm getting tired of maintaining it as part of the Gentoo kernel patch
> >set :)
> 
> Good question...  When I originally released Squashfs (Oct 2002) the 2.5 
> kernel had just gone into the feature freeze and I was waiting for the 
> unfreeze that would happen when 2.7 arrived.  As the official stance on 
> additions to 2.6 has been relaxed I have thought about submitting it.
> 
> I need to tidy up the code a bit before I submit it to the merciless 
> scrutiny of LKML :-)  Nothing bad (I hope) but there's lots of long 
> lines and I do know LKML'mers like 80 columns.
> 
> I'm planning on adding ea/acl support (people have been asking for 
> them), I can't decide whether to submit it now or wait until I've 
> finished them.  Suggestions and advice would be welcome.

Submit it now, it's self contained (doesn't patch anything outside it's
own directory), and is useful in it's current state for a lot of people.

> Slightly off topic, I've noticed you're the kernel maintainer for 
> Gentoo.  You mentioned somewhere you're down to 4 kernel patches, 
> including Squashfs? :)

Yes, squashfs is one of the four non-bugfix patches in the Gentoo kernel
2.6 kernel package.  

For those who are interested, the other three are:
	- fbsplash, the "next-gen" version of bootsplash.  No more image
	  decoders in kernelspace (compared to bootsplash), and a few
	  more features.
	- speakup, a driver package for visually-impaired users.
	- vesafb-tng, a "next-gen" version of vesafb-tng.
	- inotify.

Ok, there are now 5 patches, I forgot we addeed inotify recently to make
the Gnome developers happy.

> A lot of people/projects are now using Squashfs and it would help a
> lot of people (and me) if it did get into the kernel.  Plus it would
> be a nice thing for me anyway to have finally got it included.

I agree, it would also reduce your workload of keeping an
out-of-the-kernel fs patchset.

thanks,

greg k-h

  reply	other threads:[~2004-12-11 15:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10 20:08 [Announce] Squashfs 2.1 released (compressed filesystem) Phillip Lougher
2004-12-11  1:33 ` Greg KH
2004-12-11  5:15   ` Phillip Lougher
2004-12-11 15:39     ` Greg KH [this message]
2004-12-11 15:55       ` nat/masquerade with 2.6.x Antonio Pérez
2004-12-13  1:28         ` proc/sys/net/ipv4/tcp_bic Antonio Pérez
2004-12-12 11:01 ` [Announce] Squashfs 2.1 released (compressed filesystem) Willy Tarreau
2004-12-14  4:30   ` 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=20041211153922.GA29523@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.