mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Mickler <florian@mickler.org>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Hemminger <shemminger@vyatta.com>,
	linux-kernel@vger.kernel.org,
	Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH] [RFC] get_maintainer.pl: only list maintainers by default
Date: Sun, 9 May 2010 10:40:41 +0200	[thread overview]
Message-ID: <20100509104041.1186d5f1@schatten.dmk.lab> (raw)
In-Reply-To: <1273358674.704.77.camel@Joe-Laptop.home>

On Sat, 08 May 2010 15:44:34 -0700
Joe Perches <joe@perches.com> wrote:

> On Sat, 2010-05-08 at 23:39 +0200, florian@mickler.org wrote:
> > If scm meta-information is used, only list people that signed-off or
> > acked or reviewed the code in question.
> > 
> > after all it's called get_maintainer.pl and not
> > get_random_people_to_look_at_the_code.pl
> 
> Anyone that actually signs a patch is not "random".
> 

I actually think that tested-by and reviewed-by is not "signing",
because it is not the person who does the "tag insertion". 

it was one of the signed-off-by's who put the reviewed- and testet-tags
in there. presumably this is done in agreement with the mentioned
person. 

And for facts, please check this out:

$ git log --since=1-year-ago | grep -Pi "(reported|tested)-by:.*@"  \
 | cut -f2- -d":" | sort | uniq | wc -l
1280

so i would say, these numbers (combied with your top ten which
accounts for only 318 signatures ) suggest that those mentioned with
these tag's are one-off bug reporters and not maintainers.

cheers,
Flo

  parent reply	other threads:[~2010-05-09  8:40 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  1:57 [PATCH] epoll: use wrapper functions Changli Gao
2010-05-06  6:00 ` indiscriminate get_maintainer.pl usage (was [PATCH] epoll: use wrapper functions) Stefan Richter
     [not found]   ` <s2t412e6f7f1005052319sdbf3fdfbg256d11b983c4f304@mail.gmail.com>
2010-05-06  6:40     ` indiscriminate get_maintainer.pl usage Stefan Richter
2010-05-06 15:42       ` Davide Libenzi
2010-05-06 16:52         ` Joe Perches
2010-05-06 17:59           ` Davide Libenzi
2010-05-06 20:52             ` Joe Perches
2010-05-07  6:34               ` [PATCH] get_maintainer.pl: ignore non-maintainer tags florian
2010-05-07  6:39                 ` Joe Perches
2010-05-07  7:02                   ` Florian Mickler
2010-05-07 19:48                     ` Stefan Richter
2010-05-08 21:32                       ` [PATCH] get_maintainer.pl: optionally " florian
2010-05-08 21:39                         ` [PATCH] [RFC] get_maintainer.pl: only list maintainers by default florian
2010-05-08 22:44                           ` Joe Perches
2010-05-08 23:23                             ` Stefan Richter
2010-05-08 23:51                               ` Joe Perches
2010-05-09  0:22                                 ` Stefan Richter
2010-05-09  0:57                                   ` Joe Perches
2010-05-09  8:18                                     ` Stefan Richter
2010-05-09  8:41                                       ` Stefan Richter
2010-05-09  8:49                                     ` Florian Mickler
2010-05-09  9:12                                     ` Stefan Richter
2010-05-09  8:40                             ` Florian Mickler [this message]
2010-05-08 22:06                         ` [PATCH] get_maintainer.pl: optionally ignore non-maintainer tags Joe Perches
2010-05-09  9:15                           ` [PATCH v2] " florian
2010-05-09  9:35                             ` Stefan Richter
2010-05-10  4:56                             ` [PATCH 0/2] scripts/get_maintainer.pl: trivial improvements Joe Perches
2010-05-10  4:56                               ` [PATCH 1/2] scripts/get_maintainer.pl: optionally ignore non-maintainer signatures Joe Perches
2010-05-10  5:07                                 ` Florian Mickler
2010-05-11  6:36                                 ` [PATCH] scripts/get_maintainer.pl: default to not include unspecified tags florian
2010-05-11  7:48                                   ` Wolfram Sang
2010-05-11 15:59                                   ` Joe Perches
2010-05-11 16:33                                     ` Florian Mickler
2010-05-11 16:40                                       ` Joe Perches
2010-05-10  4:56                               ` [PATCH 2/2] scripts/get_maintainer.pl: add .get_maintainer.conf default options file Joe Perches
2010-05-12  6:30                                 ` Américo Wang
2010-05-12  9:25                                   ` Florian Mickler
2010-05-13 15:58                                     ` Américo Wang
2010-05-13 16:22                                       ` Joe Perches
2010-05-08 22:26                         ` [PATCH] " Joe Perches
2010-05-09  9:12                           ` Florian Mickler
2010-05-06 20:13       ` indiscriminate get_maintainer.pl usage Roland Dreier
2010-05-06 18:47 ` [PATCH] epoll: use wrapper functions Davide Libenzi
2010-05-06 18:51   ` Peter Zijlstra
2010-05-07  2:48     ` Changli Gao

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=20100509104041.1186d5f1@schatten.dmk.lab \
    --to=florian@mickler.org \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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

Powered by JetHome