[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1239675430.32203.116.camel@localhost>
Date: Mon, 13 Apr 2009 19:17:10 -0700
From: Joe Perches <joe@...ches.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Christoph Hellwig <hch@....de>, torvalds@...l.org,
roland@...hat.com, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>
Subject: Re: [PATCH] add ptrace entry to MAINTAINERS
On Tue, 2009-04-14 at 02:42 +0200, Ingo Molnar wrote:
> * Christoph Hellwig <hch@....de> wrote:
>
> > At the LF collab summit we decided to make Roland official ptrace
> > maintainer not just the defacto one he has been for a couple of years
> > now.
> >
> > Signed-off-by: Christoph Hellwig <hch@....de>
>
> Hm, what is this "LF collab summit" that makes decisions in terms of
> who maintains what? Some new buerocracy on top of Linux i have not
> heard about yet? :)
I think the MAINTAINERS file could
use a new status type.
These are the status types today:
Supported: Someone is actually paid to look after this.
Maintained: Someone actually looks after it.
Odd Fixes: It has a maintainer but they don't have time to do
much other than throw the odd patch in. See below..
Orphan: No current maintainer [but maybe you could take the
role as you write your new code].
Obsolete: Old code. Something tagged obsolete generally means
it has been replaced by a better system and you
should be using that.
Maybe it'd be useful to have a defined
aggregator/overseer/gatekeeper role.
Basically what Greg Kroah-Hartman does for staging
and David Miller does for driver/net
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists