On 2 July 2010 21:47, Eugene Sajine <euguess@xxxxxxxxx> wrote: > On Fri, Jul 2, 2010 at 3:18 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> Eugene Sajine <euguess@xxxxxxxxx> writes: >> >>> For example, so i could say >>> $ git config --global hooks.dir ~/git/hooks >> >> I don't think "global" hooks are useful for people who work on more than >> one project, or people who interact in more than one ways to projects. >> Different projects typically have different needs out of the hooks >> (e.g. pre-commit policy), and different workflows typically call for >> different needs out of the hooks (e.g. I would want to be able to rebase >> in my private working repository but not in the repository I use for >> integration of other people's branches). >> >> So I am fairly negative on your particular example above. > > > Well, you forgot about another half of users that are working with > many projects but using one policy for example in one company, $work is like this. Any repo on our version control host will share a common set of hooks. yves -- perl -Mre=debug -e "/just|another|perl|hacker/" -- 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