From: "Darrick J. Wong" <djwong@us.ibm.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org, cmm@us.ibm.com,
ext2-devel@lists.sourceforge.net, Alex Tomas <alex@clusterfs.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] [PATCH 1/9] extents for ext4
Date: Sat, 12 Aug 2006 10:43:04 -0700 [thread overview]
Message-ID: <44DE1328.5080101@us.ibm.com> (raw)
In-Reply-To: <20060811230239.c89394b0.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> Uh, yes. Well, I don't really care for the "ext3dev" name, but
> I tried to ignore that "feature" and fix it up anyway.
> Feel free to ignore any parts that you don't want.
Three nits to pick:
> + renamed ext4 fs later, once ext3dev is mature and stabled.
I think you want "stabilized", not "stabled".
(Until someone writes horsefs, that is. ;))
> + Other than extent maps and 48-bit block number, ext3dev also is
"...48-bit block numbers..."
> + By default the debugging output will be turned off.
"By default, the..."
--D
next prev parent reply other threads:[~2006-08-12 17:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 1:20 [PATCH 1/9] extents for ext4 Mingming Cao
2006-08-10 1:20 ` Mingming Cao
2006-08-10 6:39 ` Andrew Morton
2006-08-10 6:39 ` Andrew Morton
2006-08-10 9:29 ` [Ext2-devel] " Alex Tomas
2006-08-10 9:29 ` Alex Tomas
2006-08-10 9:48 ` [Ext2-devel] " Andrew Morton
2006-08-10 9:48 ` Andrew Morton
2006-08-10 10:08 ` [Ext2-devel] " Alex Tomas
2006-08-10 10:08 ` Alex Tomas
2006-08-10 15:55 ` [Ext2-devel] " Zach Brown
2006-08-10 15:55 ` Zach Brown
2006-08-10 17:49 ` [Ext2-devel] " Randy.Dunlap
2006-08-10 19:05 ` Alex Tomas
2006-08-10 19:05 ` Alex Tomas
2006-08-11 20:57 ` [Ext2-devel] " Randy.Dunlap
2006-08-11 20:57 ` Randy.Dunlap
2006-08-11 21:05 ` [Ext2-devel] " Alex Tomas
2006-08-11 21:05 ` Alex Tomas
2006-08-11 21:49 ` [Ext2-devel] " Mingming Cao
2006-08-11 23:00 ` Andrew Morton
2006-08-11 23:00 ` Andrew Morton
2006-08-12 6:02 ` [Ext2-devel] " Randy.Dunlap
2006-08-12 17:43 ` Darrick J. Wong [this message]
2006-08-12 18:20 ` Randy.Dunlap
2006-08-12 18:20 ` Randy.Dunlap
2006-08-14 16:26 ` [Ext2-devel] " Mingming Cao
2006-08-14 17:22 ` Randy.Dunlap
2006-08-14 17:22 ` Randy.Dunlap
2006-08-14 17:52 ` [Ext2-devel] " Jeff Garzik
2006-08-14 18:05 ` Randy.Dunlap
2006-08-14 18:13 ` Jeff Garzik
2006-08-14 18:13 ` Jeff Garzik
2006-08-15 15:40 ` [Ext2-devel] " Pavel Machek
2006-08-18 13:08 ` Andreas Dilger
2006-08-10 16:46 ` Mingming Cao
2006-08-10 16:46 ` Mingming Cao
2006-08-10 17:17 ` [Ext2-devel] " Theodore Tso
2006-08-10 17:17 ` Theodore Tso
2006-08-10 18:00 ` [Ext2-devel] " Andrew Morton
2006-08-10 18:00 ` Andrew Morton
2006-08-11 22:13 ` [Ext2-devel] " Mingming Cao
2006-08-11 22:13 ` Mingming Cao
2006-08-11 23:16 ` [Ext2-devel] " Andrew Morton
2006-08-11 23:16 ` Andrew Morton
2006-08-12 0:05 ` [PATCH 1/2] ext3 and jbd cleanup: remove whitespace Mingming Cao
2006-08-12 0:05 ` [PATCH 2/2] ext3 and jbd cleanup: replace brelse() to put_bh Mingming Cao
-- strict thread matches above, loose matches on Subject: below --
2006-08-15 21:27 [Ext2-devel] [PATCH 1/9] extents for ext4 Randy Dunlap
2006-08-15 23:19 ` Mingming Cao
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=44DE1328.5080101@us.ibm.com \
--to=djwong@us.ibm.com \
--cc=akpm@osdl.org \
--cc=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.