From: Ben Dooks <ben-linux@fluff.org>
To: linux-arm-kernel@lists.infradead.org,
Linux Samsung SoC <linux-samsung-soc@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: git pre-commit hook running checkpatch.pl
Date: Wed, 20 Jan 2010 02:02:02 +0000 [thread overview]
Message-ID: <20100120020202.GE26562@trinity.fluff.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
I've written a git pre-commit[1] hook which stops any commits happening if
checkpatch.pl reports problems with the patch. Any comments?
[1] http://www.fluff.org/ben/linux/githooks/pre-commit
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: git pre-commit hook running checkpatch.pl
Date: Wed, 20 Jan 2010 02:02:02 +0000 [thread overview]
Message-ID: <20100120020202.GE26562@trinity.fluff.org> (raw)
I've written a git pre-commit[1] hook which stops any commits happening if
checkpatch.pl reports problems with the patch. Any comments?
[1] http://www.fluff.org/ben/linux/githooks/pre-commit
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100120/e12ebdf8/attachment.sig>
next reply other threads:[~2010-01-20 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 2:02 Ben Dooks [this message]
2010-01-20 2:02 ` git pre-commit hook running checkpatch.pl Ben Dooks
2010-01-20 10:00 ` Russell King - ARM Linux
2010-01-20 10:00 ` Russell King - ARM Linux
2010-01-20 10:01 ` Mark Brown
2010-01-20 10:01 ` Mark Brown
2010-01-20 15:30 ` Uwe Kleine-König
2010-01-20 15:30 ` Uwe Kleine-König
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=20100120020202.GE26562@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.