Stefano Lattarini bf7b0e0358 maint: don't reset PATH in the commit-msg git hook ...

I have a custom 'editor' script in ~/bin, and a system-provided
'editor' program in /usr/bin (on Debian, this is a link set up the
"debian alternatives" subsystem).  My '$EDITOR' and '$GIT_EDITOR'
variables are set simply to 'editor' (no absolute path), which I
expect should point to my 'editor' script, since ~/bin precedes
/usr/bin in my PATH definition.  But the 'commit-msg' hook used in
coreutils unconditionally resets its PATH to '/bin:/usr/bin', which
causes it to call the "wrong" editor (the one in /usr/bin, not the
one in ~/bin) when it makes me update a botched commit message.

* scripts/git-hooks: Don't reset $ENV{PATH} to '/bin:/usr/bin',
which was only done to avoid failure when enabling Perl's taint
checking.

2013-02-18 01:27:47 +00:00

..

applypatch-msg

maint: add git hook scripts

2011-10-23 11:44:40 +02:00

commit-msg

maint: don't reset PATH in the commit-msg git hook

2013-02-18 01:27:47 +00:00

pre-applypatch

maint: add rule to ensure that our commit hook copies are up to date

2011-11-12 22:23:09 +01:00

pre-commit

maint: sync pre-commit script with git's

2011-11-12 14:00:18 +01:00