Han-Wen Nienhuys <hanwen@xxxxxxxxx> wrote: > > git-sh-setup isn't a 'normal' binary, in that it should be called by > bash only and not run in a subshell. Therefore, it should not be installed > in a executable directory, but rather in $prefix/share/git-core/ This seems to break existing hooks, or at least old repositories can be stuck using an old version of git-sh-setup in those hooks. You could to add GIT_datadir to PATH before invoking hooks for existing ones to work, or write some sort of conversion script... > --- > Makefile | 10 ++++++++-- > git-am.sh | 2 +- > git-applymbox.sh | 2 +- > git-applypatch.sh | 2 +- > git-bisect.sh | 2 +- > git-checkout.sh | 2 +- > git-clean.sh | 2 +- > git-commit.sh | 2 +- > git-fetch.sh | 2 +- > git-instaweb.sh | 2 +- > git-lost-found.sh | 2 +- > git-merge.sh | 2 +- > git-pull.sh | 2 +- > git-quiltimport.sh | 2 +- > git-rebase.sh | 2 +- > git-repack.sh | 2 +- > git-request-pull.sh | 2 +- > git-reset.sh | 2 +- > git-resolve.sh | 2 +- > git-revert.sh | 2 +- > git-tag.sh | 2 +- > git-verify-tag.sh | 2 +- > 22 files changed, 29 insertions(+), 23 deletions(-) You shoudl probably change these, too: templates/hooks--pre-applypatch:. git-sh-setup templates/hooks--applypatch-msg:. git-sh-setup -- Eric Wong - 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