Re: global hooks - once again
- From
- demerphq <demerphq@gmail.com>
- Date
- Jul 6, 2010, 14:34 UTC
- Message-ID
- <AANLkTilP1tyHxdirhW08FZ-bzSxSCO-rH26uPBqIV2l2@mail.gmail.com>
- In-Reply-To
- <AANLkTikMEDUI7d5Mzwm8r43zCYTqefyI06PHOMvT1iLz@mail.gmail.com>
On 2 July 2010 21:47, Eugene Sajine <euguess@gmail.com> wrote:
Show 19 quoted lines
> On Fri, Jul 2, 2010 at 3:18 PM, Junio C Hamano <gitster@pobox.com> wrote: >> Eugene Sajine <euguess@gmail.com> 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/"