On Sat, 23 Mar 2013, Tomi Ollila <tomi.ollila at iki.fi> wrote: > It is easier to enable git standard pre-commit hook, when the > operation to do so is presented. > --- > devel/STYLE | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/devel/STYLE b/devel/STYLE > index 0792ba1..92de42c 100644 > --- a/devel/STYLE > +++ b/devel/STYLE > @@ -45,8 +45,9 @@ function (param_type param, param_type param) > - likewise, there is a space following keywords such as if and while > - every binary operator should have space on either side. > > -* No trailing whitespace. Please enable the standard pre-commit hook > - in git (or an equivalent hook). > +* No trailing whitespace. Please enable the standard pre-commit hook in git > + (or an equivalent hook). The standard pre-commit hook is enabled by simply > + renaming file '.git/hooks/pre-commit.sample' to '.git/hooks/pre-commit' .
<bikeshedding> Or just refer to http://git-scm.com/book/en/Customizing-Git-Git-Hooks or man githooks if you really need to. Older versions of git used to have properly named hooks with the executable bit unset... Personally I wouldn't ask anyone to enable the hook because I wouldn't enable it in the first place. There's $EDITOR and 'git diff --check' to do that kind of thing... When I want to commit I want to commit, warts and all, and I don't want a hook to prevent me from doing so! </bikeshedding> BR, Jani.
