commit triggers.

I've grepped around, and come up with nothing, so hopefully I'm not overlooking some already-implemented feature (though it'd be great if I am). How much work is involved in creating a mechanism where some scripts living in say .git/triggers/ get executed on commits ?

The idea behind this stems from some scripts I've been running periodically against an mbox of the daily kernel commits, which greps for common bugs; kmalloc(GFP, size) instead of kmalloc(size,GFP), memsets with reversed 2nd/3rd args etc etc.

It'd be useful I think to have a way to hook up such a script to git's commit process that aborts a commit if a script returns a hit, forcing the user to fix up the mistake before committing it to the world.

thoughts ?

		Dave