From: "Matt D. Robinson" <yakker@alacritech.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Cristiano Paris <c.paris@libero.it>, linux-kernel@vger.kernel.org
Subject: Re: libz, libbz2, ramfs and cramfs
Date: Tue, 16 Oct 2001 00:32:45 -0700 [thread overview]
Message-ID: <3BCBE29D.CFEC1F05@alacritech.com> (raw)
In-Reply-To: <19978.1003206943@kao2.melbourne.sgi.com>
Keith Owens wrote:
> On Mon, 15 Oct 2001 15:06:42 +0200 (CEST),
> Cristiano Paris <c.paris@libero.it> wrote:
> >I'm interested in developing a file system which could take features from
> >ramfs and cramfs so I have a couple of questions which possibly Linus
> >would answer to.
> >Second, quoting from the jffs2's TODO list :
> >
> >- fix zlib. It's ugly as hell and there are at least three copies in the
> >kernel tree
>
> The -ac tree is moving to a single copy of zlib, in fs/inflate_fs. It
> is currently used by cramfs and zisofs. jffs2 in the -ac tree still
> uses its own copy of zlib and should be converted.
Any plans to fix this for the Linus tree? Also, why place this in fs?
Shouldn't this be around for PPP along with other things that
can use it (like LKCD)?
--Matt
next prev parent reply other threads:[~2001-10-16 7:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 13:06 libz, libbz2, ramfs and cramfs Cristiano Paris
2001-10-15 22:53 ` H. Peter Anvin
2001-10-16 4:35 ` Keith Owens
2001-10-16 7:32 ` Matt D. Robinson [this message]
2001-10-17 8:31 ` H. Peter Anvin
2001-10-18 3:04 ` Paul Mackerras
2001-10-18 3:25 ` H. Peter Anvin
2001-10-18 7:15 ` Paul Mackerras
2001-10-18 12:15 ` Paul Mackerras
2001-10-18 17:33 ` H. Peter Anvin
2001-10-17 8:45 ` David Woodhouse
2001-10-16 17:36 ` David Woodhouse
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=3BCBE29D.CFEC1F05@alacritech.com \
--to=yakker@alacritech.com \
--cc=c.paris@libero.it \
--cc=kaos@ocs.com.au \
--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