# git-* in hook scripts 4 messages from 2010-02-23 to 2010-02-25. Participants: Eli Barzilay, Miklos Vajna, Junio C Hamano. Thread: https://gitlist.dev/t/22768 ## Eli Barzilay, 2010-02-23 16:33 Subject: git-* in hook scripts Message-ID: URL: https://gitlist.dev/e/m3hbp7x673.fsf%40winooski.ccs.neu.edu ``` 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! ``` ## Miklos Vajna, 2010-02-23 23:59 Subject: Re: git-* in hook scripts Message-ID: <20100223235941.GG12429@genesis.frugalware.org> URL: https://gitlist.dev/e/20100223235941.GG12429%40genesis.frugalware.org In-Reply-To: ``` On Tue, Feb 23, 2010 at 11:33:36AM -0500, Eli Barzilay 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. ``` ## Junio C Hamano, 2010-02-24 00:32 Subject: Re: git-* in hook scripts Message-ID: <7vr5obxyln.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vr5obxyln.fsf%40alter.siamese.dyndns.org In-Reply-To: <20100223235941.GG12429@genesis.frugalware.org> ``` Miklos Vajna writes: > On Tue, Feb 23, 2010 at 11:33:36AM -0500, Eli Barzilay 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. We have been waiting until nobody remembers days we had dashes. It may be a good time to at least start thinking about updating them. v1.6.0 is one year and half old. ``` ## Eli Barzilay, 2010-02-25 07:15 Subject: Re: git-* in hook scripts Message-ID: URL: https://gitlist.dev/e/m38wahwzuu.fsf%40winooski.ccs.neu.edu In-Reply-To: <20100223235941.GG12429@genesis.frugalware.org> ``` Miklos Vajna writes: > On Tue, Feb 23, 2010 at 11:33:36AM -0500, Eli Barzilay 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. 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! ```