From: Jeff Garzik <jeff@garzik.org>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: akpm@osdl.org, Theodore Tso <tytso@mit.edu>,
ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Mingming Cao <cmm@us.ibm.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/5] Register ext3dev filesystem
Date: Thu, 10 Aug 2006 16:27:29 -0400 [thread overview]
Message-ID: <44DB96B1.6040304@garzik.org> (raw)
In-Reply-To: <20060810202307.GB12766@harddisk-recovery.com>
Erik Mouw wrote:
> So what about "ext4dev"? That shows that the filesystem is not ext3 and
> experimental.
<shrug> Whatever people prefer most.
The important point is that CONFIG_EXPERIMENTAL isn't enough.
Jeff
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-08-10 20:27 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 [this message]
2006-08-15 15:25 ` Pavel Machek
2006-11-20 10:14 ` Sander
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=44DB96B1.6040304@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=erik@harddisk-recovery.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).