From: Andrew Morton <akpm@osdl.org>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: suparna@in.ibm.com, ext4 development <linux-ext4@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [RFC] [PATCH] Documentation/filesystems/ext4.txt
Date: Tue, 10 Oct 2006 13:56:40 -0700 [thread overview]
Message-ID: <20061010135640.f82061f9.akpm@osdl.org> (raw)
In-Reply-To: <1160510555.28923.15.camel@kleikamp.austin.ibm.com>
On Tue, 10 Oct 2006 15:02:35 -0500
Dave Kleikamp <shaggy@austin.ibm.com> wrote:
> > > Hopefully not :)
> > > We should be able to put something together for a start. Where should this
> > > reside ? Under Documentation/filesystems/ext4.txt ?
>
> Suparna put this together and I updated it a bit.
Great, thanks.
> > That sounds appropriate. And in the patch changelog.
>
> How do you want to handle the patch set? I could resend it with more
> comments, put it into git, or do you just want to plug the comments into
> the patches you are carrying? I can do whatever works best for you.
I'll just send what I have now in the next batch, probably this evening.
> + - Grab updated e2fsprogs from
> + ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs-interim/
> + This is a patchset on top of e2fsprogs-1.39, which can be found at
> + ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/
Could we please get a patched tarball up there? The easier we make it for
our testers, the more we get.
next prev parent reply other threads:[~2006-10-10 20:56 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
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 [this message]
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=20061010135640.f82061f9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
--cc=suparna@in.ibm.com \
--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