From: Sander <sander@humilis.net>
To: Mingming Cao <cmm@us.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/5] Register ext3dev filesystem
Date: Mon, 20 Nov 2006 11:14:31 +0100 [thread overview]
Message-ID: <20061120101431.GA8831@favonius> (raw)
In-Reply-To: <1155172642.3161.74.camel@localhost.localdomain>
Mingming Cao wrote (ao):
> Register ext4 filesystem as ext3dev filesystem in kernel.
[cut]
> diff -puN fs/Kconfig~register-ext3dev fs/Kconfig
> --- linux-2.6.18-rc4/fs/Kconfig~register-ext3dev 2006-08-09 15:41:29.277105718 -0700
> +++ linux-2.6.18-rc4-ming/fs/Kconfig 2006-08-09 15:41:29.321106074 -0700
> @@ -138,6 +138,72 @@ config EXT3_FS_SECURITY
> If you are not using a security module that requires using
> extended attributes for file security labels, say N.
>
> +config EXT3DEV_FS
> + tristate "Developmenting extended fs support"
> + select JBD
> + help
> + Ext3dev is a precede filesystem toward next generation
> + of extended fs, based on ext3 filesystem code. It will be
> + renamed ext4 fs later once this ext3dev is mature and stabled.
[cut]
> + To compile this file system support as a module, choose M here: the
> + module will be called ext2. Be aware however that the file system
^^^^
This should be 'ext4'?
With kind regards, Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
prev parent reply other threads:[~2006-11-20 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 1:17 [PATCH 2/5] Register ext3dev filesystem Mingming Cao
2006-08-10 9:20 ` [Ext2-devel] " Erik Mouw
2006-08-10 17:33 ` Randy.Dunlap
2006-08-10 17:59 ` Theodore Tso
2006-08-10 19:53 ` Jeff Garzik
2006-08-10 20:08 ` Dave Kleikamp
2006-08-10 20:22 ` John Stoffel
2006-08-10 20:24 ` Jeff Garzik
2006-08-10 21:05 ` Mingming Cao
2006-08-10 20:23 ` Erik Mouw
2006-08-10 20:27 ` Jeff Garzik
2006-08-15 15:25 ` Pavel Machek
2006-11-20 10:14 ` Sander [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=20061120101431.GA8831@favonius \
--to=sander@humilis.net \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).