From: Roberto Di Cosmo <Roberto.Di-Cosmo@pps.jussieu.fr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: pavel@suse.cz (Pavel Machek),
Roberto.Di-Cosmo@pps.jussieu.fr (Roberto Di Cosmo),
linux-kernel@vger.kernel.org, demolinux@demolinux.org,
dicosmo@pps.jussieu.fr
Subject: Re: [isocompr PATCH]: announcing stable port to kernel 2.2.18
Date: Wed, 13 Jun 2001 16:38:34 +0200 (CEST) [thread overview]
Message-ID: <15143.31466.157254.112437@beryllium.pps.jussieu.fr> (raw)
In-Reply-To: <E159r4y-0001bR-00@the-village.bc.nu>
In-Reply-To: <20010611225944.B959@bug.ucw.cz> <E159r4y-0001bR-00@the-village.bc.nu>
I was not aware of the zisofs patch... I will be looking at it
in these days, and try to compare it to the isocompr patch (that
was also brought to our attention by people on the list quite a long
time ago, but we only ended up fixing it recently :-)).
I will keep you posted on the results (this does not prevent others
from doing the comparison, of course, but I promise to post a result
soon)
--Roberto
>>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> > sometime in the future (I have been looking at 2.4.x code, but the new
>> page > cache means some changes might be needed: I will try to post a
>> first version > for 2.4.x soon).
>>
>> I think that 2.5.0 should be your target... It is definitely new feature,
>> and both 2.4.X and 2.2.X are in feature freeze.
Alan> How is it different to HPA's zisofs which already exists for 2.4 ?
next prev parent reply other threads:[~2001-06-13 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 9:29 Roberto Di Cosmo
2001-06-11 20:59 ` Pavel Machek
2001-06-12 9:53 ` Ingo Oeser
2001-06-12 16:31 ` Alan Cox
2001-06-13 14:38 ` Roberto Di Cosmo [this message]
2001-06-17 14:42 ` [isocompr PATCH]: first comparison with HPA's zisofs Roberto Di Cosmo
2001-06-17 17:03 ` H. Peter Anvin
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=15143.31466.157254.112437@beryllium.pps.jussieu.fr \
--to=roberto.di-cosmo@pps.jussieu.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=demolinux@demolinux.org \
--cc=dicosmo@pps.jussieu.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=roberto@dicosmo.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®