3 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Eli Barzilay <hidden>
Date: 2016-06-15 22:48:20
There are several sample hook scripts that use `git-*' -- should these
use `git *' instead?
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
From: Miklos Vajna <hidden>
Date: 2016-06-15 22:48:20
On Tue, Feb 23, 2010 at 11:33:36AM -0500, Eli Barzilay [off-list ref] wrote:
There are several sample hook scripts that use `git-*' -- should these use `git *' instead?
No need to do so, `git --exec-path` is already in PATH when those scripts are invoked.
From: Eli Barzilay <hidden>
Date: 2016-06-15 22:48:21
Miklos Vajna [off-list ref] writes:
On Tue, Feb 23, 2010 at 11:33:36AM -0500, Eli Barzilay [off-list ref] wrote:quoted
There are several sample hook scripts that use `git-*' -- should these use `git *' instead?No need to do so, `git --exec-path` is already in PATH when those scripts are invoked.
To make this a little more concrete, I was thinking about the fact
that `git cmd' can be different from `git-cmd' if I add a file with
the second name for one of the builtin commands.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!