public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
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 08:26:39 +0000	[thread overview]
Message-ID: <20081120082639.GC14274@shadowen.org> (raw)
In-Reply-To: <19f34abd0811181420i2b582fd2jcaa685b0cbb5c979@mail.gmail.com>

On Tue, Nov 18, 2008 at 11:20:48PM +0100, Vegard Nossum wrote:
> Hi,
> 
> 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.

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.

-apw

  reply	other threads:[~2008-11-20  8:26 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 [this message]
2008-11-20  8:57   ` Vegard Nossum
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=20081120082639.GC14274@shadowen.org \
    --to=apw@shadowen.org \
    --cc=julia@diku.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vegard.nossum@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