The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: paulmck@linux.vnet.ibm.com
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, mingo@kernel.org,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
	sbw@mit.edu
Subject: Re: [PATCH tip/core/rcu 2/3] rcu: Add designated reviewers for RCU
Date: Tue, 08 Jul 2014 15:05:16 -0700	[thread overview]
Message-ID: <1404857116.932.68.camel@joe-AO725> (raw)
In-Reply-To: <20140708215229.GA4603@linux.vnet.ibm.com>

On Tue, 2014-07-08 at 14:52 -0700, Paul E. McKenney wrote:
> On Tue, Jul 08, 2014 at 02:01:04PM -0700, Joe Perches wrote:
> > On Tue, 2014-07-08 at 13:41 -0700, Paul E. McKenney wrote:
[]
> > > scripts: Teach get_maintainer.pl about the new "R:" tag
> 
> [ . . . ]
> 
> > Paul, I already sent you a better version over a month ago.
> 
> That would explain why I had already forgotten about it.  ;-)
> 
> > https://lkml.org/lkml/2014/6/2/585

Too bad because you added your own "tested-by"
in a reply. :p

> Unless you tell me otherwise, I assume that this means that you are
> OK with my adding your Signed-off-by to that patch.  (The lack thereof
> being another reason I would not have queued it.)  Please see below for
> the proposed commit log and Signed-off-by.
> 
> If you don't tell me otherwise, I will submit this to the next merge
> window.

Swell.

I still think the concept is pretty useless and it's
just a duplication of "M:", which isn't anything other
than a list of who should be sent patches.

MAINTAINERS describes the "M:" letter as just:

	M: Mail patches to: FullName <address@domain>

It doesn't describe anything like a pull hierarchy
or even describe actual maintainership.

But if "R:" is going to go in, then get_maintainers
should be updated at the same time.

btw: most "M:" entries aren't actual maintainers.

Maybe those non-maintainer "M:" entries should be
converted to the "R:" category and "M:" should
only be used to describe for the pull hierarchy.



  reply	other threads:[~2014-07-08 22:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 22:41 [PATCH tip/core/rcu 0/3] Maintainership changes for 3.17 Paul E. McKenney
2014-07-07 22:42 ` [PATCH tip/core/rcu 1/3] MAINTAINERS: Add "R:" designated-reviewers tag Paul E. McKenney
2014-07-07 22:42   ` [PATCH tip/core/rcu 2/3] rcu: Add designated reviewers for RCU Paul E. McKenney
2014-07-08  8:09     ` Peter Zijlstra
2014-07-08 18:06       ` Joe Perches
2014-07-08 20:41         ` Paul E. McKenney
2014-07-08 21:01           ` Joe Perches
2014-07-08 21:52             ` Paul E. McKenney
2014-07-08 22:05               ` Joe Perches [this message]
2014-07-08 22:25                 ` Paul E. McKenney
2014-07-09  4:09                   ` Joe Perches
2014-07-09 11:14                     ` Paul E. McKenney
2014-07-09 13:23                       ` Joe Perches
2014-07-10  9:39                         ` Peter Zijlstra
2014-07-10 10:00                           ` Joe Perches
2014-07-10 23:16                             ` josh
2014-07-11  8:32                               ` Peter Zijlstra
2014-07-09 17:00                     ` josh
2014-07-09 17:13                       ` Joe Perches
2014-07-09 17:42                     ` Frederic Weisbecker
2014-07-09 18:10                       ` Joe Perches
2014-07-07 22:42   ` [PATCH tip/core/rcu 3/3] rcu: Update RCU maintainership Paul E. McKenney
2014-07-08 17:58     ` Josh Triplett
2014-07-08 20:47       ` Paul E. McKenney
2014-07-07 22:55 ` [PATCH tip/core/rcu 0/3] Maintainership changes for 3.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=1404857116.932.68.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhart@linux.intel.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=niv@us.ibm.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sbw@mit.edu \
    --cc=tglx@linutronix.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