From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Andy Whitcroft" <apw@shadowen.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Julia Lawall" <julia@diku.dk>
Subject: Re: gitwatch: RSS feed of checkpatch+coccinelle against new commits in mainline
Date: Thu, 20 Nov 2008 09:57:14 +0100 [thread overview]
Message-ID: <19f34abd0811200057n73cfae6va5efc1d91bc438e4@mail.gmail.com> (raw)
In-Reply-To: <20081120082639.GC14274@shadowen.org>
On Thu, Nov 20, 2008 at 9:26 AM, Andy Whitcroft <apw@shadowen.org> wrote:
> On Tue, Nov 18, 2008 at 11:20:48PM +0100, Vegard Nossum wrote:
>> I've written a script that follows the mainline git repository and
>> runs checkpatch against all new commits. The result is available as an
>> RSS stream:
>>
>> http://kernel.org/~vegard/gitwatch.rss
>>
>> Only commits with warnings or errors are shown. Files that change are
>> also searched for known/frequent coding errors using Coccinelle and a
>> selection of the semantic patches found on the Coccinelle website.
>
> Thats pretty intresting. Looking at some of the cochinelle output I am
> a little confused as to what its saying. Am I right in thinking that
> for those reports that a proposed patch is printed, after the comment
> for the original patch? If so it might be helpful to say something like
> 'proposed modificiation' just before the patchlet.
You are correct, those are the modifications that would have been made
by the semantic patch. I agree, it might look like the log text
belongs to the patch below, which is wrong. We are also planning to
add a description to each of the semantic patches so that a better
explanation is given for the change.
> Also which version of checkpatch is this output being generated with?
> The one at the head of the git tree or something else? I see a couple
> of false positives in there that I know I have fixed already.
Yes, it's a copy of the one in linux-2.6.git (after v2.6.28-rc4). The
file itself says 0.24. Which false positives were you thinking about?
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-11-20 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 22:20 gitwatch: RSS feed of checkpatch+coccinelle against new commits in mainline Vegard Nossum
2008-11-20 8:26 ` Andy Whitcroft
2008-11-20 8:57 ` Vegard Nossum [this message]
2008-11-20 9:07 ` Andy Whitcroft
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=19f34abd0811200057n73cfae6va5efc1d91bc438e4@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=apw@shadowen.org \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
/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