it would be really nice to have in my ~/.gitconfig something that could
override the location of the hooks dir normally in .git/hooks.  the only
way i can think of currently doing this is overriding the default templates,
but this only works for new repos.

- -- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages git-core depends on:
ii  libc6                  2.9-12            GNU C Library: Shared libraries
ii  libcurl3-gnutls        7.19.4-1          Multi-protocol file transfer libra
ii  libdigest-sha1-perl    2.11-2+b1         NIST SHA-1 message digest algorith
ii  liberror-perl          0.17-1            Perl module for error/exception ha
ii  libexpat1              2.0.1-4           XML parsing C library - runtime li
ii  perl-modules           5.10.0-22         Core Perl modules
ii  zlib1g                 1:1.2.3.3.dfsg-13 compression library - runtime

Versions of packages git-core recommends:
ii  less                        429-2        pager program similar to more
ii  openssh-client [ssh-client] 1:5.1p1-5+b1 secure shell client, an rlogin/rsh
ii  patch                       2.5.9-5      Apply a diff file to an original
ii  rsync                       3.0.5-1      fast remote file copy program (lik

Versions of packages git-core suggests:
pn  git-arch                      <none>     (no description available)
pn  git-cvs                       <none>     (no description available)
pn  git-daemon-run                <none>     (no description available)
pn  git-doc                       <none>     (no description available)
ii  git-email                     1:1.6.3-1  fast, scalable, distributed revisi
ii  git-gui                       1:1.6.3-1  fast, scalable, distributed revisi
ii  git-svn                       1:1.6.3-1  fast, scalable, distributed revisi
ii  gitk                          1:1.6.3-1  fast, scalable, distributed revisi
pn  gitweb                        <none>     (no description available)

- -- no debconf information
iD8DBQFKCIWpynjLPm522B0RAqRYAJ9n5C5fcXt8HNjlfwo8ntnMROLlzwCfZCxV
KP8Tudu27jvTOsDuK9WZqLo=
=6AaG
-----END PGP SIGNATURE-----

found 528270 git/1:1.7.2.3-2.1
tags 528270 - fixed-upstream
forwarded 528270 http://thread.gmane.org/gmane.comp.version-control.git/150141/focus=150346
quit

sean finney wrote:

This is a complicated one.  The main problem is that each repository
might need slightly different hooks, so a global collection of hooks
would be problematic unless combined with some per-repository
configuration.

The best solution currently available is to set up the directory
pointed to by "[init] templatedir" to contain a symlink in place of
the hooks directory.  This does not work retroactively on existing
repositories but it does make it easy to understand what has happened
and to be able to easily tweak the behavior without walking
repositories from then on.  A script involving "find -name .git" can
be used to take care of existing repos on the day it is set up.