From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Roberto Di Cosmo <Roberto.Di-Cosmo@pps.jussieu.fr>,
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: Tue, 12 Jun 2001 11:53:38 +0200 [thread overview]
Message-ID: <20010612115338.J754@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <200106110929.f5B9T5Q27584@foobar.pps.jussieu.fr> <20010611225944.B959@bug.ucw.cz>
In-Reply-To: <20010611225944.B959@bug.ucw.cz>; from pavel@suse.cz on Mon, Jun 11, 2001 at 10:59:44PM +0200
On Mon, Jun 11, 2001 at 10:59:44PM +0200, Pavel Machek wrote:
> > The current version of the patch for 2.2.18 is very stable
> > (we use it for DemoLinux [see www.demolinux.org] heavily),
> > and I wonder if it could not be a good idea to see if this
> > code can be folded into the official releases 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.
Right. And besides: HPA coded a similar patch for 2.4.x, while he
fixed some issues.
So you might try his work or even come to an agreement on the
format.
Regards
Ingo Oeser
--
Use ReiserFS to get a faster fsck and Ext2 to fsck slowly and gently.
next prev parent reply other threads:[~2001-06-12 9:56 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 [this message]
2001-06-12 16:31 ` Alan Cox
2001-06-13 14:38 ` Roberto Di Cosmo
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=20010612115338.J754@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=Roberto.Di-Cosmo@pps.jussieu.fr \
--cc=demolinux@demolinux.org \
--cc=dicosmo@pps.jussieu.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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®