mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean <seanlkml@sympatico.ca>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andy Whitcroft <apw@shadowen.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	roel <12o3l@tiscali.nl>, lkml <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@xenotime.net>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] spin_lock_unlocked cleanups
Date: Fri, 28 Sep 2007 17:15:23 -0400	[thread overview]
Message-ID: <BAYC1-PASMTP03BE3FCD597E8017F583D1AEB20@CEZ.ICE> (raw)
In-Reply-To: <1190970369.18681.17.camel@chaos>

On Fri, 28 Sep 2007 11:06:09 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:

> > The problem with git-commit is who's repo to add the hook to.  I did
> > attempt to do this by picking up each of linus' main releases and then
> > using the git blame engine to attribute each "failure" to a particular
> > commit.  The plan then would be to send a nasty-gram to the committer
> > about violations there-in.

Wouldn't it be easier to pass each commit through checkpatch and
email the committer if there is a problem?  Each commit can be viewed
as a standalone patch afterall; what does blame add?

> The question is, whether we can convince the git developers to integrate
> it. When a commit happens and checkpatch.pl is in scripts/, then run the
> patch through it before doing the actual commit.

Definitely the way to go.  I'm pretty sure the Git guys would agree to
distribute checkpatch.pl along with the existing pre-commit hook.  So
at least enabling checkpatch would be trivial for those convinced to
use it.

Sean

  reply	other threads:[~2007-09-28 21:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 21:36 roel
2007-09-28  8:17 ` Thomas Gleixner
2007-09-28  8:26   ` Andrew Morton
2007-09-28  8:30     ` Ingo Molnar
2007-09-28  8:55       ` Andrew Morton
2007-09-28  8:32     ` Thomas Gleixner
2007-09-28  8:56       ` Andy Whitcroft
2007-09-28  9:06         ` Thomas Gleixner
2007-09-28 21:15           ` Sean [this message]
2007-09-28  8:53     ` Andy Whitcroft
2007-09-28  9:05       ` Andrew Morton
2007-09-28 17:31     ` Mark Gross

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=BAYC1-PASMTP03BE3FCD597E8017F583D1AEB20@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=12o3l@tiscali.nl \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®