On Mon, Jul 5, 2010 at 12:03, Peter Kjellerstedt <peter.kjellerstedt@xxxxxxxx> wrote: > So what I have done is setup a template directory with hooks being > a link to a pre-installed directory, where each hook is linked to a > single script. This script then reads from a directory called > hooks.d which is a drop directory for hooks. Each hook then has the > format '<hook>.<order>.<name>' (e.g., 'post-receive.10.send_mail'), > somewhat similar to /etc/rcX.d. It will also look in a .githooks.d > directory in the working directory (this can be disabled with a > config option). This is used by repository owners who want to add > extra hooks for their repositories, e.g., to add automatic code > indentation before commit, or unit testing. It is also possible > to specify more hook directories with a multi-value config option, > which the user can use if he/she likes to add some personal hooks. How do your users disable execution of global hooks in this scheme? (to protect themselves from an evil system administrator) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html