From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] Squashfs pull request for 2.6.29
Date: Fri, 09 Jan 2009 02:11:26 +0000 [thread overview]
Message-ID: <4966B24E.1050700@lougher.demon.co.uk> (raw)
In-Reply-To: <20090108175338.2abbee16.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 8 Jan 2009 11:50:29 -0500 Christoph Hellwig <hch@infradead.org> wrote:
>
>> On Thu, Jan 08, 2009 at 04:48:51PM +0000, Phillip Lougher wrote:
>>> Please consider pulling my linux-next branch
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/pkl/squashfs-linus.git
>>>
>>> The patches have been posted to LKML and linux-fsdevel over the last
>>> couple of months and have been reviewed and changed as requested.
>>> Diffstat below.
>>>
>>> Squashfs is a compressed read-only filesystem. It compresses metadata
>>> and data, and uses up to 1 MiB block sizes for greater compression.
>> That seems pretty fast for something only posted this week and not
>> even in -next.
>
> I discussed this with Phillip a bit, and it looks like we'll go for a
> 2.6.21 merge. This gives a couple of months for testing and review in
> linux-next.
>
> Of course, this assumes that someone will actually perform that testing
> and review. Chances are that it'll just sit there, getting nothing more
> than compilation testing.
Yes please review! If people feels it needs a couple more months in
linux-next with more in-depth review then I'll live with that. I'll
fix anything more that comes up, because I'm desperate to get it
mainlined. I've lived the last couple of years with constant
moaning from people that I've not mainlined it, and I took
the last six months off work to work on it full time to get
it into shape to mainline.
Hopefully now it's at least in sufficient shape to go into
Linux-next I can get another job, and get some income which
will be nice.
>
> Apparently I reviewed the code a while back - that grey cell must have
> died. Does anyone else intend to review the code in that timeframe?
> If not, we might as well merge it now, if ever..
>
I'll be very happy for a merge now, but of course it's not up to me :-(
Phillip
>
next prev parent reply other threads:[~2009-01-09 2:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 16:48 Phillip Lougher
2009-01-08 16:50 ` Christoph Hellwig
2009-01-08 17:05 ` Phillip Lougher
2009-01-08 17:11 ` Geert Uytterhoeven
2009-01-08 23:55 ` H. Peter Anvin
2009-01-09 1:53 ` Andrew Morton
2009-01-09 2:11 ` Phillip Lougher [this message]
2009-01-09 2:24 ` Kay Sievers
2009-01-09 2:36 ` Phil Oester
2009-01-09 16:54 ` Jörn Engel
2009-01-09 19:37 ` David Brown
2009-01-09 21:19 ` Jörn Engel
2009-01-10 12:43 ` Ingo Molnar
2009-01-10 16:50 ` Jörn Engel
2009-01-10 18:12 ` Andrew Morton
2009-01-10 18:30 ` Linus Torvalds
2009-01-10 19:57 ` Jeff Garzik
2009-01-10 20:16 ` Leon Woestenberg
2009-01-11 6:36 ` Valdis.Kletnieks
2009-01-10 19:19 ` Olivier Galibert
2009-01-10 22:15 ` Ingo Molnar
2009-01-11 9:30 ` Geert Uytterhoeven
2009-01-11 15:39 ` Ingo Molnar
2009-01-11 16:30 ` Greg KH
2009-01-22 21:50 ` Dave Jones
2009-01-22 21:57 ` Randy Dunlap
2009-01-22 22:15 ` Greg KH
2009-01-22 21:58 ` Greg KH
2009-01-22 22:26 ` Ingo Molnar
2009-01-22 22:50 ` Kyle McMartin
2009-01-22 23:04 ` Greg KH
2009-01-22 23:25 ` Evgeniy Polyakov
2009-01-22 23:34 ` Kyle McMartin
2009-01-22 23:41 ` Ingo Molnar
2009-01-22 23:28 ` Evgeniy Polyakov
2009-01-22 22:16 ` Ingo Molnar
2009-01-22 22:24 ` Pekka Enberg
2009-01-23 0:16 ` Andrew Morton
2009-01-23 0:30 ` Greg KH
2009-01-09 2:30 ` Harvey Harrison
2009-01-09 11:25 ` KOSAKI Motohiro
2009-01-09 12:02 ` Alan Cox
2009-01-09 21:56 ` Linus Torvalds
2009-01-09 22:08 ` Andrew Morton
2009-01-09 22:12 ` Linus Torvalds
2009-01-09 22:26 ` Alan Cox
2009-01-09 22:36 ` Harvey Harrison
2009-01-11 3:01 ` Phillip Lougher
2009-01-11 3:06 ` H. Peter Anvin
2009-01-09 16:32 ` Geert Uytterhoeven
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=4966B24E.1050700@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®