From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Kleikamp <shaggy@austin.ibm.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Updated ext4/jbd2 patches based on 2.6.19-rc1
Date: Tue, 10 Oct 2006 13:24:02 +0530 [thread overview]
Message-ID: <20061010075402.GA23992@in.ibm.com> (raw)
In-Reply-To: <20061009232927.77b667c2.akpm@osdl.org>
On Mon, Oct 09, 2006 at 11:29:27PM -0700, Andrew Morton wrote:
> On Thu, 5 Oct 2006 17:39:33 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>
> > Could we please have a few nice words about ext4 for the record? Like,
> > what its features are, how one creates an instance, where to get the
> > correct userspace tools from, stability level, any known shortcomings,
> > issues, etc?
>
> So I guess I get to write this.
Hopefully not :)
We should be able to put something together for a start. Where should this
reside ? Under Documentation/filesystems/ext4.txt ?
However, since this is still very clearly a "development" branch at the moment,
with lots of ongoing work both on the kernel and even more so on the
tools side, how much detail are you looking for ?
Regards
Suparna
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
next prev parent reply other threads:[~2006-10-10 7:51 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 18:23 Updated ext4/jbd2 patches based on 2.6.19-rc1 Dave Kleikamp
2006-10-05 20:19 ` Andrew Morton
2006-10-05 23:25 ` Linus Torvalds
2006-10-06 12:50 ` Dave Kleikamp
2006-10-06 16:11 ` Linus Torvalds
2006-10-05 21:59 ` Andrew Morton
2006-10-06 0:39 ` Andrew Morton
2006-10-10 6:29 ` Andrew Morton
2006-10-10 7:54 ` Suparna Bhattacharya [this message]
2006-10-10 8:14 ` Andrew Morton
2006-10-10 20:02 ` [RFC] [PATCH] Documentation/filesystems/ext4.txt Dave Kleikamp
2006-10-10 20:56 ` Andrew Morton
2006-10-11 17:03 ` Andreas Dilger
2006-10-12 14:18 ` Valerie Clement
2006-10-06 3:55 ` Updated ext4/jbd2 patches based on 2.6.19-rc1 Andrew Morton
2006-10-06 3:58 ` Andrew Morton
2006-10-06 10:34 ` Alex Tomas
2006-10-06 4:54 ` Randy Dunlap
2006-10-06 5:05 ` Andrew Morton
2006-10-06 5:53 ` Andreas Dilger
2006-10-06 6:04 ` Andrew Morton
2006-10-06 6:41 ` Andreas Dilger
2006-10-06 6:50 ` Andrew Morton
2006-10-06 10:31 ` Alex Tomas
2006-10-06 13:57 ` Andrew Morton
2006-10-07 20:09 ` alex
2006-10-06 6:52 ` Suparna Bhattacharya
2006-10-06 12:21 ` Theodore Tso
2006-10-06 21:10 ` [PATCH] Get rid of extents mount option Dave Kleikamp
2006-10-06 21:21 ` [PATCH] Get rid of extents mount option - try 2 Dave Kleikamp
2006-10-06 22:32 ` Andrew Morton
2006-10-06 23:20 ` Dave Kleikamp
2006-10-07 4:14 ` Theodore Tso
2006-10-07 15:53 ` Dave Kleikamp
2006-10-07 17:20 ` Theodore Tso
2006-10-07 19:45 ` Alex Tomas
2006-10-07 19:57 ` Andrew Morton
2006-10-10 18:48 ` Dave Kleikamp
2006-10-10 21:07 ` Theodore Tso
2006-10-10 21:18 ` Andrew Morton
2006-10-11 17:16 ` Andreas Dilger
2006-10-06 4:31 ` Updated ext4/jbd2 patches based on 2.6.19-rc1 Andrew Morton
2006-10-06 5:58 ` Andreas Dilger
2006-10-06 6:10 ` Andrew Morton
2006-10-06 6:48 ` Andreas Dilger
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=20061010075402.GA23992@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
/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