From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Start using the 'reviewer' (R) tag
Date: Wed, 28 Oct 2015 04:06:39 -0700 [thread overview]
Message-ID: <1446030399.2757.83.camel@perches.com> (raw)
In-Reply-To: <CABxcv=mzzcx3o0m3hYzcn0DyM2pEFDZ-ZgVCjChWGf+y4Xy78A@mail.gmail.com>
On Wed, 2015-10-28 at 11:53 +0100, Javier Martinez Canillas wrote:
> (Lee) think(s) that the difference between a maintainer and
> a reviewer is if a branch with fixes / new features are kept and pull
> requests sent while I think that the difference is the level of
> involvement someone has with a driver regardless of how patches ends
> in the subsystem tree (picked directly by subsystem maintainers or
> sent through pull requests).
>
> Is the first time I heard your definition but maybe I'm the one that
> is wrong so it would be great to get a consensus on that and get it
> documented somewhere.
I think Lee is over-analyzing.
>From MAINTAINERS:
M: Mail patches to: FullName <address@domain>
R: Designated reviewer: FullName <address@domain>
These reviewers should be CCed on patches.
S: Status, one of the following:
Supported: Someone is actually paid to look after this.
Maintained: Someone actually looks after it.
"looking after" doesn't mean upstreaming.
The original threads for this were:
http://lists.linuxfoundation.org/pipermail/ksummit-discuss/2014-May/000830.html
https://lkml.org/lkml/2014/6/2/446
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Wolfram Sang <wsa@the-dreams.de>,
Linus Walleij <linus.walleij@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Mark Brown <broonie@kernel.org>, Ben Dooks <ben-linux@fluff.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] MAINTAINERS: Start using the 'reviewer' (R) tag
Date: Wed, 28 Oct 2015 04:06:39 -0700 [thread overview]
Message-ID: <1446030399.2757.83.camel@perches.com> (raw)
In-Reply-To: <CABxcv=mzzcx3o0m3hYzcn0DyM2pEFDZ-ZgVCjChWGf+y4Xy78A@mail.gmail.com>
On Wed, 2015-10-28 at 11:53 +0100, Javier Martinez Canillas wrote:
> (Lee) think(s) that the difference between a maintainer and
> a reviewer is if a branch with fixes / new features are kept and pull
> requests sent while I think that the difference is the level of
> involvement someone has with a driver regardless of how patches ends
> in the subsystem tree (picked directly by subsystem maintainers or
> sent through pull requests).
>
> Is the first time I heard your definition but maybe I'm the one that
> is wrong so it would be great to get a consensus on that and get it
> documented somewhere.
I think Lee is over-analyzing.
>From MAINTAINERS:
M: Mail patches to: FullName <address@domain>
R: Designated reviewer: FullName <address@domain>
These reviewers should be CCed on patches.
S: Status, one of the following:
Supported: Someone is actually paid to look after this.
Maintained: Someone actually looks after it.
"looking after" doesn't mean upstreaming.
The original threads for this were:
http://lists.linuxfoundation.org/pipermail/ksummit-discuss/2014-May/000830.html
https://lkml.org/lkml/2014/6/2/446
next prev parent reply other threads:[~2015-10-28 11:06 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 15:42 [PATCH] MAINTAINERS: Start using the 'reviewer' (R) tag Lee Jones
2015-10-27 15:42 ` Lee Jones
2015-10-27 17:24 ` Sebastian Reichel
2015-10-27 17:24 ` Sebastian Reichel
2015-10-27 18:15 ` Lee Jones
2015-10-27 18:15 ` Lee Jones
2015-10-27 18:44 ` Joe Perches
2015-10-27 18:44 ` Joe Perches
2015-10-28 1:46 ` Krzysztof Kozlowski
2015-10-28 1:46 ` Krzysztof Kozlowski
2015-10-28 8:24 ` Lee Jones
2015-10-28 8:24 ` Lee Jones
2015-10-28 9:21 ` Javier Martinez Canillas
2015-10-28 9:21 ` Javier Martinez Canillas
2015-10-28 9:25 ` Javier Martinez Canillas
2015-10-28 9:25 ` Javier Martinez Canillas
2015-10-28 9:31 ` Krzysztof Kozlowski
2015-10-28 9:31 ` Krzysztof Kozlowski
2015-10-28 10:28 ` Lee Jones
2015-10-28 10:28 ` Lee Jones
2015-10-28 10:53 ` Javier Martinez Canillas
2015-10-28 10:53 ` Javier Martinez Canillas
2015-10-28 11:06 ` Joe Perches [this message]
2015-10-28 11:06 ` Joe Perches
2015-10-28 11:25 ` Javier Martinez Canillas
2015-10-28 11:25 ` Javier Martinez Canillas
2015-10-28 11:39 ` Lee Jones
2015-10-28 11:39 ` Lee Jones
2015-10-28 12:14 ` Lee Jones
2015-10-28 12:14 ` Lee Jones
2015-10-28 12:20 ` Joe Perches
2015-10-28 12:20 ` Joe Perches
2015-10-28 12:24 ` Lee Jones
2015-10-28 12:24 ` Lee Jones
2015-10-28 12:46 ` Joe Perches
2015-10-28 12:46 ` Joe Perches
2015-10-28 13:06 ` Javier Martinez Canillas
2015-10-28 13:06 ` Javier Martinez Canillas
2015-10-28 13:34 ` Lee Jones
2015-10-28 13:34 ` Lee Jones
2015-10-28 14:09 ` Javier Martinez Canillas
2015-10-28 14:09 ` Javier Martinez Canillas
2015-10-28 14:38 ` Lee Jones
2015-10-28 14:38 ` Lee Jones
2015-10-28 14:54 ` Javier Martinez Canillas
2015-10-28 14:54 ` Javier Martinez Canillas
2015-10-28 23:56 ` Krzysztof Kozlowski
2015-10-28 23:56 ` Krzysztof Kozlowski
2015-10-29 0:12 ` Javier Martinez Canillas
2015-10-29 0:12 ` Javier Martinez Canillas
2015-10-30 16:51 ` Lee Jones
2015-10-30 16:51 ` Lee Jones
2015-10-30 16:51 ` Lee Jones
2015-10-30 16:51 ` Lee Jones
2015-10-28 9:23 ` Krzysztof Kozlowski
2015-10-28 9:23 ` Krzysztof Kozlowski
2015-10-28 9:39 ` Uwe Kleine-König
2015-10-28 9:39 ` Uwe Kleine-König
2015-10-28 9:55 ` Lee Jones
2015-10-28 9:55 ` Lee Jones
2015-10-28 13:13 ` Krzysztof Kozlowski
2015-10-28 13:13 ` Krzysztof Kozlowski
2015-10-28 16:41 ` [PATCH] get_maintainer: Add subsystem to reviewer output Joe Perches
2015-10-28 16:41 ` Joe Perches
2015-10-28 17:01 ` Lee Jones
2015-10-28 17:01 ` Lee Jones
2015-10-28 17:08 ` Joe Perches
2015-10-28 17:08 ` Joe Perches
2015-10-28 17:22 ` Lee Jones
2015-10-28 17:22 ` Lee Jones
2015-10-28 17:30 ` Joe Perches
2015-10-28 17:30 ` Joe Perches
2015-10-28 17:49 ` Lee Jones
2015-10-28 17:49 ` Lee Jones
2015-10-28 17:56 ` Joe Perches
2015-10-28 17:56 ` Joe Perches
2015-10-29 9:20 ` Lee Jones
2015-10-29 9:20 ` Lee Jones
2015-10-29 14:14 ` Joe Perches
2015-10-29 14:14 ` Joe Perches
2015-10-29 16:17 ` Lee Jones
2015-10-29 16:17 ` Lee Jones
2015-10-28 17:18 ` Joe Perches
2015-10-28 17:18 ` Joe Perches
2015-10-28 23:49 ` Krzysztof Kozlowski
2015-10-28 23:49 ` Krzysztof Kozlowski
2015-10-28 10:14 ` [PATCH] MAINTAINERS: Start using the 'reviewer' (R) tag Lee Jones
2015-10-28 10:14 ` Lee Jones
2015-10-28 13:27 ` Krzysztof Kozlowski
2015-10-28 13:27 ` Krzysztof Kozlowski
2015-10-28 13:49 ` Lee Jones
2015-10-28 13:49 ` Lee Jones
2015-10-28 16:26 ` Bartlomiej Zolnierkiewicz
2015-10-28 16:26 ` Bartlomiej Zolnierkiewicz
2015-10-28 16:33 ` Lee Jones
2015-10-28 16:33 ` Lee Jones
2015-10-28 8:57 ` Chanwoo Choi
2015-10-28 8:57 ` Chanwoo Choi
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=1446030399.2757.83.camel@perches.com \
--to=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.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 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.