public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: josh@joshtriplett.org
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	Dave Chinner <david@fromorbit.com>, Joe Perches <joe@perches.com>,
	paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org,
	dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
	fweisbec@gmail.com, oleg@redhat.com, sbw@mit.edu
Subject: Re: [PATCH RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag
Date: Tue, 3 Jun 2014 15:08:50 -0700	[thread overview]
Message-ID: <20140603220850.GA20736@cloud> (raw)
In-Reply-To: <20140603174631.2de89352@gandalf.local.home>

On Tue, Jun 03, 2014 at 05:46:31PM -0400, Steven Rostedt wrote:
> On Tue, 3 Jun 2014 16:52:53 -0400
> Theodore Ts'o <tytso@mit.edu> wrote:
> 
> 
> > The important thing to note here is that we do not have consensus
> > across all subsystems what Reviewed-by: means, and I think that's OK.
> > The Reviewed-by: is mostly of interest to the maintainer before the
> > patch is submitted to mainline.  The value of keeping it in the git
> > commit logs after the fact seems to be a bit variable, although if
> > there are companies blindly using it as a performance metric and this
> > is driving down the quality of reviews, perhaps one could even argue
> > that including these tags in the git commit logs is actually adding
> > negative value.  But I don't really care about that issue, because
> > like most maintainers, I know the reviewers by reputation, and whether
> > someone actually says "you can add my Reviewed-by" is actually not so
> > important as their comments on the patch, one way or another.
> 
> I prefer the Reviewed-by tags in the git commit. If something is
> screwed up in a commit, I can blame the reviewers just as much as I can
> blame the author :-)

I like it there for the same reason: if there turns out to be an issue
in a commit I reviewed, I'd like to get CCed on the resulting discussion
and fix, so that I can take that into account in future reviews.

- Josh Triplett

  reply	other threads:[~2014-06-03 22:13 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 17:00 [PATCH RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag Paul E. McKenney
2014-06-02 17:00 ` [PATCH RFC 2/2] rcu: Add Josh Triplett as designated reviewer Paul E. McKenney
2014-06-02 20:35   ` Andrew Morton
2014-06-02 20:36     ` Joe Perches
2014-06-02 20:38       ` Randy Dunlap
2014-06-03  0:02         ` josh
2014-06-03  1:07           ` Randy Dunlap
2014-06-03  1:51             ` Josh Triplett
2014-06-03  3:11               ` Joe Perches
2014-06-03  5:10                 ` Josh Triplett
2014-06-03  5:21                   ` Joe Perches
2014-06-03 17:21               ` Randy Dunlap
2014-06-02 17:22 ` [PATCH RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag Joe Perches
2014-06-02 17:29   ` Steven Rostedt
2014-06-02 17:34     ` Joe Perches
2014-06-02 17:48   ` josh
2014-06-02 17:59     ` Joe Perches
2014-06-02 18:12       ` Josh Boyer
2014-06-02 18:15         ` Joe Perches
2014-06-02 18:16       ` Paul E. McKenney
2014-06-02 18:44         ` Joe Perches
2014-06-02 18:50           ` Steven Rostedt
2014-06-02 18:55             ` josh
2014-06-02 19:05               ` Joe Perches
2014-06-02 19:09                 ` josh
2014-06-02 19:17                   ` Joe Perches
2014-06-02 23:19                     ` Dave Chinner
2014-06-02 23:24                       ` Andrew Morton
2014-06-03  0:35                         ` Steven Rostedt
2014-06-02 23:59                       ` josh
2014-06-03  0:12                         ` Joe Perches
2014-06-03 23:48                           ` Ken Moffat
2014-06-04  0:03                             ` Steven Rostedt
2014-06-04  0:33                             ` Joe Perches
2014-06-03  1:11                         ` Dave Chinner
2014-06-03  1:30                           ` Steven Rostedt
2014-06-03  7:16                             ` Dave Chinner
2014-06-03 13:24                               ` Mathieu Desnoyers
2014-06-03 15:54                                 ` Paul E. McKenney
2014-06-03 17:43                               ` Steven Rostedt
2014-06-03 18:05                                 ` Randy Dunlap
2014-06-03 20:52                                 ` Theodore Ts'o
2014-06-03 21:46                                   ` Steven Rostedt
2014-06-03 22:08                                     ` josh [this message]
2014-06-05  4:01                                 ` Dave Chinner
2014-06-05 21:14                                   ` Frank Rowand
2014-06-02 19:26                 ` Paul E. McKenney
2014-06-02 20:41                   ` Dipankar Sarma
2014-06-02 19:07             ` Paul E. McKenney
2014-06-02 18:56         ` josh
2014-06-02 19:08           ` Paul E. McKenney
2014-06-02 19:11             ` josh
2014-06-02 19:27               ` Paul E. McKenney
2014-06-02 19:36                 ` Joe Perches
2014-06-02 19:40                   ` Randy Dunlap
2014-06-02 20:29                     ` josh
2014-06-02 19:50                   ` Paul E. McKenney
2014-06-02 19:55                     ` Joe Perches
2014-06-02 20:07                       ` Paul E. McKenney
2014-06-02 20:25                 ` Mathieu Desnoyers
2014-06-03 15:37                   ` Paul E. McKenney
2014-06-03 16:16                     ` Steven Rostedt
2014-06-03 16:25                       ` Paul E. McKenney
2014-06-04  1:35                 ` Lai Jiangshan

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=20140603220850.GA20736@cloud \
    --to=josh@joshtriplett.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhart@linux.intel.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=joe@perches.com \
    --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 \
    --cc=tytso@mit.edu \
    /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