From: Tom Rini <trini@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Sverker Wiberg <Sverker.Wiberg@uab.ericsson.se>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Multiple zlib.c's in 2.4.18
Date: Sat, 13 Apr 2002 14:27:57 -0700 [thread overview]
Message-ID: <20020413212757.GF10015@opus.bloom.county> (raw)
In-Reply-To: <3CB6F332.18225BA4@uab.ericsson.se> <E16wSTJ-0000qU-00@the-village.bc.nu>
On Sat, Apr 13, 2002 at 07:42:01PM +0100, Alan Cox wrote:
> > Further checking reveals that ./arch/ppc/boot/lib/zlib.c is based on
> > zlib-0.95, while the other two are zlib-1.0.4.
> >
> > Which one should I use? Shouldn't they be merged? And what about the
> > double-free() bug?
>
> There is progress going on to merge them (see 2.4.19-ac) so hopefully RSN
> that question won't be worth asking.
All of them that can be anyhow. I'm hoping no one will touch
arch/ppc/boot/lib/zlib.c :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2002-04-13 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 14:46 Multiple zlib.c's in 2.4.18 Sverker Wiberg
2002-04-13 18:42 ` Alan Cox
2002-04-13 21:27 ` Tom Rini [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=20020413212757.GF10015@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=Sverker.Wiberg@uab.ericsson.se \
--cc=alan@lxorguk.ukuu.org.uk \
--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