From: Jonathan Nieder <jrnieder@gmail.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: global hooks - once again
Date: Fri, 2 Jul 2010 13:03:55 -0500 [thread overview]
Message-ID: <20100702180355.GA1770@burratino> (raw)
In-Reply-To: <AANLkTikXJS5QCXMXgsOfkYn9cMBQV6o23tds5YG3A_OI@mail.gmail.com>
Eugene Sajine wrote:
> I have found a thread dated March 2008 about the subject, but there
> was no acceptable solution provided.
Link?
> If there is no better way now Is it possible to create a git config
> property specifying where the global hooks folder is and then look for
> hooks there first and then in the repo or vice versa?
Well, I like the idea[1]. The design issues are not very complicated;
the main thing is to implement it.
$ git grep -l -F -e 'hooks/' -- \*.c \*.sh \*.perl | egrep -v '^(contrib/(examples|hooks))|t/'
builtin/commit.c
builtin/init-db.c
builtin/receive-pack.c
git-am.sh
git-cvsserver.perl
git-rebase--interactive.sh
git-rebase.sh
run-command.c
Hope that helps,
Jonathan
[1] e.g., for http://bugs.debian.org/514651
next prev parent reply other threads:[~2010-07-02 18:04 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100702180355.GA1770@burratino \
--to=jrnieder@gmail.com \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).