public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@lst.de>,
	torvalds@osdl.org, roland@redhat.com,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] add ptrace entry to MAINTAINERS
Date: Mon, 13 Apr 2009 19:17:10 -0700	[thread overview]
Message-ID: <1239675430.32203.116.camel@localhost> (raw)
In-Reply-To: <20090414004231.GA17288@elte.hu>

On Tue, 2009-04-14 at 02:42 +0200, Ingo Molnar wrote:
> * Christoph Hellwig <hch@lst.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@lst.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



      parent reply	other threads:[~2009-04-14  2:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 15:20 [PATCH] add ptrace entry to MAINTAINERS Christoph Hellwig
2009-04-14  0:30 ` Joe Perches
2009-04-14  0:42 ` Ingo Molnar
2009-04-14  1:14   ` Roland McGrath
2009-04-14  1:22   ` Oleg Nesterov
2009-04-14  2:17   ` Joe Perches [this message]

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=1239675430.32203.116.camel@localhost \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=roland@redhat.com \
    --cc=torvalds@osdl.org \
    /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