[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120706101149.GA26028@localhost.localdomain>
Date: Fri, 6 Jul 2012 12:11:49 +0200
From: Richard Cochran <richardcochran@...il.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Glauber Costa <glommer@...allels.com>,
"J. Bruce Fields" <bfields@...ldses.org>,
Jonathan Corbet <corbet@....net>,
ksummit-2012-discuss@...ts.linux-foundation.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2012-discuss] [ATTEND or not ATTEND] That's the
question!
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@...il.com>
Tags: docu whitespace trivial
Part of the review would be making sure the labels fit.
Thanks,
Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists