From: Ingo Molnar <mingo@elte.hu>
To: Christoph Hellwig <hch@lst.de>
Cc: 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: Tue, 14 Apr 2009 02:42:31 +0200 [thread overview]
Message-ID: <20090414004231.GA17288@elte.hu> (raw)
In-Reply-To: <20090413152010.GA16682@lst.de>
* 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? :)
Because you got your facts wrong: the real ptrace de-facto
maintainer is Oleg Nesterov and Andrew Morton, as per
kernel/ptrace.c and arch/x86/kernel/ptrace.c signoffs since v2.6.27:
2 Tejun Heo
2 WANG Cong
3 Roland McGrath
4 David Howells
5 James Morris
6 Oleg Nesterov
7 Andrew Morton
9 Linus Torvalds
9 Markus Metzger
22 Ingo Molnar
Oleg has been doing most of the heavy lifting in terms of reviewing
patches, acking patches and most importantly: keeping bad patches
out of the ptrace code - in the past year or so.
Although i would certainly not mind Roland getting more active in
this space either :)
But in terms of fairness, if you so conveniently 'decide' who
maintains ptrace then Oleg is a must-have maintainer in that space
too.
Ingo
next prev parent reply other threads:[~2009-04-14 0:43 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 [this message]
2009-04-14 1:14 ` Roland McGrath
2009-04-14 1:22 ` Oleg Nesterov
2009-04-14 2:17 ` 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=20090414004231.GA17288@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--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