From: Nicholas Wourms <nwourms@myrealbox.com>
To: linux-kernel@vger.kernel.org
Cc: Steven Cole <elenstev@mesatop.com>
Subject: Re: [Patch] 2.5.70-bk9 kick FAR out of the zlib
Date: Fri, 06 Jun 2003 10:49:09 -0400 [thread overview]
Message-ID: <3EE0A9E5.9080000@myrealbox.com> (raw)
In-Reply-To: 20030605203108.GD22439@wohnheim.fh-wedel.de
Jörn Engel wrote:
> My words were "all or nothing". Linus was against nothing, so the
> answer is all, that simple.
>
> As to your "someone comes up with a better zlib" concern, this has
> happened already. An guess what, we ignored it. So unless you come
> up with a patch to get the 1.1.4 changes into the kernel and describe
> what the two magic bits are all about, I couldn't care less.
1.1.4 would be a waste of time at this point. Better to wait for the
upcoming 1.2.x release, which promises improved performance (esp. on
x86) and better compression...
Cheers,
Nicholas
prev parent reply other threads:[~2003-06-06 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 19:46 [Patch] 2.5.70-bk9 kick FAR out of the zlib Jörn Engel
2003-06-05 20:09 ` [Patch] 2.5.70-bk9 zlib cleanup #2 ZEXTERN Jörn Engel
2003-06-05 20:18 ` [Patch] 2.5.70-bk9 zlib cleanup #3 ZEXPORT Jörn Engel
2003-06-05 20:33 ` [Patch] 2.5.70-bk9 zlib cleanup #4 z_off_t Jörn Engel
2003-06-05 20:38 ` Jörn Engel
2003-06-05 20:42 ` Jörn Engel
2003-06-05 20:49 ` [Patch] 2.5.70-bk9 zlib cleanup #5 __32BIT__ and STDC Jörn Engel
2003-06-05 21:14 ` [Patch] 2.5.70-bk9 zlib cleanup #6 OF Jörn Engel
2003-06-05 20:17 ` [Patch] 2.5.70-bk9 kick FAR out of the zlib Richard B. Johnson
2003-06-05 20:31 ` Jörn Engel
2003-06-06 14:49 ` Nicholas Wourms [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=3EE0A9E5.9080000@myrealbox.com \
--to=nwourms@myrealbox.com \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.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