Augmenting the copyright_year check to be able to check that a copyright exists for a specific entitfy for the current year.
Merge pull request #14 from pblack/copyrights_with_entity

Augmenting the copyright_year check to be able to check that a copyright...
using /usr/bin/env

bash can be placed in /usr/local/bin on FreeBSD
Merge pull request #18 from mishanga/patch-1

using /usr/bin/env
Add support for pre-push commit hook that was added in Git 1.8.2

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Use /usr/bin/env in generated hook scripts

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Fix too many hooks reported in list_hooks_in_dir

list_hooks_in_dir should report exactly the hooks that would be run with
run_hooks. But the find command in list_hooks_in_dir does not limit itself to
the scheme "folder_name/hook_name" but recurses infinitely through sub
directories reporting all executable files. If your hooks are stored itself in
a git repository then consequently also the files in .git/hooks are reported.

This change sets the search depth exactly to two, so that the correct scripts
are reported, e.g. :
    ~/.git_hooks/commit-msg/script1

but not e.g. :

    ~/.git_hook/.git/hooks/commit-msg
    ~/.git_hooks/script2
    ~/.git_hooks/commit-msg/dir2/script3

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
In the event we can't rename hooks we should immediately fail.

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
If git hooks isn't installed explicitly say how to install it

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Add support for Git on windows where find doesn't have the -L option

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Behave much better when not in a git repository
or when the repository is a bare repository

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Add the ability to remind users when committing to any repo without git-hooks.

It is easy to forget to install git-hooks in a repository you are using.
A commit with no error message could both mean you don't have git-hooks
installed and it can mean that you do have it installed, but your
commit was perfect and there was no errors.

The new option --installglobal creates a default .git template
that is used by all future cloned repositories (and git init'd)
that remind users that the repository doesn't have git-hooks
installed.

A number of projects I have been involved with used git-hooks,
but founds its weakest point was that eventually someone would
re-clone a repo and make commits with errors before turning
git-hooks back on.  Another common problem was when we had
multiple git repositories and git-hooks was only installed in
some of them, but not all

While it would be nice to be able to use --instalglobal to
automatically turn on git-hooks on every future repo eventually
some git repository on github would include a hook that would
email <secret stuff> back home and all you would have to do
would be to clone it to activate it which would be a "bad thing",
but it can pester you without harm.

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Remove .gitignore which was just ignoring vim swap files
which really belong in users global .gitignore file.

Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Updated README to use markdown & edited for grammar, phrasing, and clarity
Merge pull request #29 from Zearin/patch-1

Updated README to use markdown & edited for grammar, phrasing, and clarity
Merge remote-tracking branch 'upstream/master'

Conflicts:
	git-hooks