threads / discuss / 16737

hooks/post-update execs git-update-server-info

Subject: hooks/post-update execs git-update-server-info

## tl;dr

3 messages between Dec 15, 2008 and Dec 16, 2008.

replies: 2people: 2as markdown or json

Sitaram Chamarty· Dec 15, 2008, 16:18 UTC · lore

shouldn't .git/hooks/post-update contain "exec git update-server-info" (note the space not hyphen) instead of "exec git-update-server-info"?

Either I am horribly confused or HTTP pulls have not been working on post 1.6 gits and no one has noticed till now :-)

Jakub Narebski· Dec 15, 2008, 17:06 UTC · re: Sitaram Chamarty · lore

Re: hooks/post-update execs git-update-server-info

Sitaram Chamarty <sitaramc@gmail.com> writes:

Show 6 quoted lines

> shouldn't .git/hooks/post-update contain "exec git
> update-server-info" (note the space not hyphen) instead of
> "exec git-update-server-info"?
> 
> Either I am horribly confused or HTTP pulls have not been
> working on post 1.6 gits and no one has noticed till now :-)

If I understand correctly hooks run with GIT_EXEC_PATH prepended to PATH, so everything should work; and it has to work to not force users to upgrade their (perhaps customized) hooks after upgrading git.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

Sitaram Chamarty· Dec 16, 2008, 01:27 UTC · re: Jakub Narebski · lore

Re: hooks/post-update execs git-update-server-info

On 2008-12-15, Jakub Narebski <jnareb@gmail.com> wrote:

> Sitaram Chamarty <sitaramc@gmail.com> writes:

>> shouldn't .git/hooks/post-update contain "exec git
>> update-server-info" (note the space not hyphen) instead of

> If I understand correctly hooks run with GIT_EXEC_PATH prepended to
> PATH, so everything should work; and it has to work to not force users

you're right -- it does. There was something else wrong in my quick-and-dirty testing that caused me to jump to the wrong conclusion; sorry for the noise!