From: Mingming Cao <cmm@us.ibm.com>
To: Joe Perches <joe@perches.com>
Cc: Eric Sandeen <sandeen@redhat.com>, Theodore Tso <tytso@mit.edu>,
torvalds@linux-foundation.org, sct@redhat.com,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
akpm@linux-foundation.org, Eric Sandeen <esandeen@redhat.com>
Subject: Re: [PATCH] [188/2many] MAINTAINERS - EXT4 FILE SYSTEM
Date: Mon, 13 Aug 2007 10:19:39 -0700 [thread overview]
Message-ID: <1187025579.3876.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1187024133.10249.113.camel@localhost>
On Mon, 2007-08-13 at 09:55 -0700, Joe Perches wrote:
> On Mon, 2007-08-13 at 11:39 -0500, Eric Sandeen wrote:
> > (And to be fair about it in terms of actual work done so far, please
> > put
> > the other names ahead of mine!) :)
>
> EXT4 FILE SYSTEM
> P: Ted Ts'o
> M: tytso@mit.edu
> P: Mingming Cao
> M: cmm@us.ibm.com
> P: Andreas Dilger
> M: adilger@clusterfs.com
> P: Eric Sandeen
> M: sandeen@redhat.com
> L: linux-ext4@vger.kernel.org
> S: Maintained
> F: fs/ext4/
> F: include/linux/ext4*
>
Probably should add Shaggy (Dave Kleikamp <shaggy@austin.ibm.com>) here
too. He helped push ext4 fs into mainline and actively performing ext4
patch queue maintainence.
Mingming
next prev parent reply other threads:[~2007-08-13 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:27 [PATCH] [188/2many] MAINTAINERS - EXT4 FILE SYSTEM joe
2007-08-13 9:01 ` Andreas Dilger
2007-08-13 11:45 ` Stephen C. Tweedie
2007-08-13 15:19 ` Theodore Tso
2007-08-13 16:14 ` Joe Perches
2007-08-13 16:39 ` Eric Sandeen
2007-08-13 16:55 ` Joe Perches
2007-08-13 17:19 ` Mingming Cao [this message]
2007-08-13 18:16 ` Joe Perches
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=1187025579.3876.4.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=esandeen@redhat.com \
--cc=joe@perches.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sct@redhat.com \
--cc=torvalds@linux-foundation.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).