linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Glauber Costa <glommer@parallels.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Jonathan Corbet <corbet@lwn.net>,
	ksummit-2012-discuss@lists.linux-foundation.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2012-discuss] [ATTEND or not ATTEND] That's the question!
Date: Fri, 06 Jul 2012 16:06:55 +0530	[thread overview]
Message-ID: <4FF6BFC7.9060405@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120706101149.GA26028@localhost.localdomain>

On 07/06/2012 03:41 PM, Richard Cochran wrote:
> On Fri, Jul 06, 2012 at 11:54:52AM +0200, Frederic Weisbecker wrote:
>> On Fri, Jul 06, 2012 at 01:43:06PM +0400, Glauber Costa wrote:
>>> The same way we have checkpatch, we can have something automated that
>>> will attempt to rule out some trivial patches in the counting process.
>>> We can scan a patch, and easily determine if each part of it is:
>>>
>>> * pure whitespace
>>> * pure Documentation change
>>> * comment fix
>>>
>>> And if a patch is 100 % comprised by those, we simply don't count it.
>>> People that just want to increase their numbers - they will always
>>> exist, will tend to stop doing that. Simply because doing it will not
>>> help them at all.
>>
>> OTOH, documentation changes or comment fixes, and even sometimes pure whitespace
>> fixes, can be very valuable contributions. This can be a useful and ungrateful
>> work and that deserve credit.
>>
>> We just can't find an automated and right way to evaluate a contribution.
> 
> Well what about submitters and maintainers labeling patches below the
> SOB with tags like the following?
> 
>    Signed-off-by: Richard Cochran <richardcochran@gmail.com>
>    Tags: docu whitespace trivial
> 
> Part of the review would be making sure the labels fit.
> 

Please no!
I don't see why we should clutter the changelog with tags for reasons as
unimportant as measuring some patch's value!

Regards,
Srivatsa S. Bhat


  parent reply	other threads:[~2012-07-06 10:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 22:56 [ATTEND or not ATTEND] That's the question! Thomas Gleixner
2012-06-15 23:34 ` [Ksummit-2012-discuss] " Greg KH
2012-06-16 10:50   ` Thomas Gleixner
2012-06-16 13:29     ` Jonathan Corbet
2012-06-16 13:32       ` Frederic Weisbecker
2012-06-16 13:56       ` Rafael J. Wysocki
2012-06-17 10:40       ` Thomas Gleixner
2012-06-17 18:51         ` Greg KH
2012-06-17 18:58       ` Mark Brown
2012-06-20 19:51       ` J. Bruce Fields
2012-07-06  9:43         ` Glauber Costa
2012-07-06  9:54           ` Frederic Weisbecker
2012-07-06  9:59             ` Glauber Costa
2012-07-06 10:00             ` Srivatsa S. Bhat
2012-07-06 10:03               ` Glauber Costa
2012-07-06 10:21                 ` Srivatsa S. Bhat
2012-07-06 10:11             ` Richard Cochran
2012-07-06 10:14               ` Glauber Costa
2012-07-06 10:36               ` Srivatsa S. Bhat [this message]
2012-07-06 10:43                 ` Glauber Costa
2012-07-06 12:42                   ` Steven Rostedt
2012-07-17 22:17           ` david
2012-06-16 11:30   ` Alan Cox
2012-06-16 15:03     ` Phil Turmel
2012-06-16 16:43     ` Myklebust, Trond
2012-06-20  0:40       ` Dave Chinner
2012-06-17 17:04     ` Mark Brown
2012-06-19 15:45 ` Bjorn Helgaas
2012-06-19 19:18   ` Roland Dreier

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=4FF6BFC7.9060405@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=bfields@fieldses.org \
    --cc=corbet@lwn.net \
    --cc=fweisbec@gmail.com \
    --cc=glommer@parallels.com \
    --cc=ksummit-2012-discuss@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).