aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorGeorg Lutz <georg@georglutz.de>2013-08-24 20:17:11 +0200
committerBenjamin C Meyer <ben@meyerhome.net>2013-10-20 22:14:26 -0400
commit187f23820f43e962acbeab788d5a96d5d59bd51e (patch)
tree6dab2087cbcc058d08cb9927ebae996f0dbd8b8c /README
parent600bd81f37a059c4a16eb48fa8838750bea48e5a (diff)
downloadgit-hooks-187f23820f43e962acbeab788d5a96d5d59bd51e.tar.gz
git-hooks-187f23820f43e962acbeab788d5a96d5d59bd51e.tar.bz2
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>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions