[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1207171512130.1373@asgard.lang.hm>
Date: Tue, 17 Jul 2012 15:17:12 -0700 (PDT)
From: david@...g.hm
To: Glauber Costa <glommer@...allels.com>
cc: "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!
apologies for the late response
On Fri, 6 Jul 2012, 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.
I would look at things a bit differently.
strip out whitespace changes (they can be valuable, but usually only in
combination with other work)
added comments or documetnation count double (we always need better
documentation.
if the number of lines removed is more than a delata larger than the
number added, the patch is probably a reorginization/cleanup and should
get a boost in the metrics.
David Lang
--
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