From: Andi Drebes <lists-receive@programmierforen.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-fsdevel@vger.kernel.org, Tomas M <tomas@slax.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: cramfs in big endian
Date: Sun, 11 Nov 2007 11:20:16 +0100 [thread overview]
Message-ID: <200711111120.17004.lists-receive@programmierforen.de> (raw)
In-Reply-To: <473614E8.2010802@zytor.com>
> What about simply deep-sixing cramfs and replacing it with squashfs or
> something else?
I think this is the long term solution. Cramfs isn't a very beautiful
filesystem. It's a good candidate for removal. However, there are still some
distributions that use cramfs for initrds. So removing it immediately isn't a
good idea.
Andi
prev parent reply other threads:[~2007-11-11 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 21:16 cramfs in big endian Andi Drebes
2007-11-07 13:52 ` Tomas M
2007-11-07 20:51 ` Andi Drebes
2007-11-07 22:49 ` Christoph Hellwig
2007-11-08 18:10 ` Andi Drebes
2007-11-10 1:03 ` H. Peter Anvin
2007-11-10 15:13 ` Christoph Hellwig
2007-11-10 20:19 ` H. Peter Anvin
2007-11-10 20:26 ` Andi Drebes
2007-11-10 20:30 ` H. Peter Anvin
2007-11-11 10:20 ` Andi Drebes [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=200711111120.17004.lists-receive@programmierforen.de \
--to=lists-receive@programmierforen.de \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tomas@slax.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.