public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Cristiano Paris <c.paris@libero.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libz, libbz2, ramfs and cramfs
Date: Tue, 16 Oct 2001 14:35:43 +1000	[thread overview]
Message-ID: <19978.1003206943@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 15 Oct 2001 15:06:42 +0200." <Pine.LNX.4.33.0110151436040.755-100000@lisa.rhpk.springfield.inwind.it>

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.


  parent reply	other threads:[~2001-10-16  4:35 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 [this message]
2001-10-16  7:32   ` Matt D. Robinson
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=19978.1003206943@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=c.paris@libero.it \
    --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