From: Adrian Bunk <bunk@stusta.de>
To: Theodore Tso <tytso@mit.edu>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] fs/jbd/journal.c: possible cleanups
Date: Tue, 16 May 2006 23:33:44 +0200 [thread overview]
Message-ID: <20060516213344.GT10077@stusta.de> (raw)
In-Reply-To: <20060516211430.GA9571@thunk.org>
On Tue, May 16, 2006 at 05:14:30PM -0400, Theodore Tso wrote:
> On Tue, May 16, 2006 at 09:39:56PM +0200, Adrian Bunk wrote:
> > Since you replied to this patch:
> > Who is the subsystem maintainer for jbd?
>
> I'd suggest sending mail to ext2-devel@lists.sourceforge.net. There's
> actually a lot of work going on right now with both ext3 and jbd right
> now, including finally getting the 64-bit support for jbd merged in.
What about getting a MAINTAINERS entry for jbd?
The only current entry listing ext2-devel@lists.sourceforge.net is for
ext2 which doesn't use jbd...
> - Ted
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-05-16 21:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 17:44 [RFC: 2.6 patch] fs/jbd/journal.c: possible cleanups Adrian Bunk
2006-05-16 19:27 ` Andrew Morton
2006-05-16 19:39 ` Adrian Bunk
2006-05-16 19:50 ` Andrew Morton
2006-05-18 11:52 ` Stephen C. Tweedie
2006-05-16 21:14 ` Theodore Tso
2006-05-16 21:33 ` Adrian Bunk [this message]
2006-05-16 22:26 ` [PATCH] Update ext2/ext3/jbd MAINTAINERS entries Theodore Tso
2006-05-18 11:48 ` Stephen C. Tweedie
2006-05-17 1:33 ` [RFC: 2.6 patch] fs/jbd/journal.c: possible cleanups Arjan van de Ven
2006-05-17 1:40 ` Andrew Morton
2006-05-17 1:51 ` Arjan van de Ven
2006-05-17 1:58 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-05-01 7:11 Adrian Bunk
2006-04-23 11:49 Adrian Bunk
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=20060516213344.GT10077@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.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 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.