From: demerphq <demerphq@gmail.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: global hooks - once again
Date: Tue, 6 Jul 2010 16:34:27 +0200 [thread overview]
Message-ID: <AANLkTilP1tyHxdirhW08FZ-bzSxSCO-rH26uPBqIV2l2@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikMEDUI7d5Mzwm8r43zCYTqefyI06PHOMvT1iLz@mail.gmail.com>
On 2 July 2010 21:47, Eugene Sajine <euguess@gmail.com> wrote:
> 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/"
next prev parent reply other threads:[~2010-07-06 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 16:23 global hooks - once again Eugene Sajine
2010-07-02 18:03 ` Jonathan Nieder
2010-07-02 19:30 ` Eugene Sajine
2010-07-02 19:18 ` Junio C Hamano
2010-07-02 19:47 ` Eugene Sajine
2010-07-05 10:03 ` Peter Kjellerstedt
2010-07-06 12:14 ` Alex Riesen
2010-07-06 12:23 ` Eugene Sajine
2010-07-06 14:55 ` Peter Kjellerstedt
2010-07-06 15:00 ` demerphq
2010-07-06 15:32 ` Eugene Sajine
2010-07-06 12:20 ` Eugene Sajine
2010-07-06 14:34 ` demerphq [this message]
2010-07-02 20:53 ` Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilP1tyHxdirhW08FZ-bzSxSCO-rH26uPBqIV2l2@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).