Re: Unable to coax hooks into working

> 
> On Apr 27, 2010, at 10:52 AM, Michael J Gruber wrote:
>> Jeremiah Foster venit, vidit, dixit 27.04.2010 10:33:
>>> 
>>> On Apr 26, 2010, at 8:11 PM, Jacob Helwig wrote:
>>>> 
>>>> You want one of the receive, or update hooks, if you're
>>>> putting this in a central place, where it needs to be triggered
>>>> by someone doing a push in to the repo.
>>> 
>>> Thanks Jacob. I'd just like to confirm that I am, in fact, using
>>> the update hook. I logged into the server holding the git repo,
>>> cd'd to
>> 
>> That used to be different ;) update hook on the server is good.
>> 
>>> the .git/hooks/ directory. Moved the update.sample to update.
>>> Changed the code to something trivial that would echo back to the
>>> client for testing. I checked permissions, checked ownership, ran
>>> the code as the git repo owner. I logged out, did a trivial
>>> change in the client repo, ran git commit -a -m "foo" and
>>> expected that the trivial update script to run on the server
>>> would produce output to the client. This
>> 
>> But this is the same problem backwards. Again: Please try to
>> understand what commit does, and what push does, in terms of where
>> (local repo vs. server) a change happens:
> 
> I think I do. The commit pushes the change onto the index. The index
> is local. It gets pushed to the remote server when I do a git push. I
> should have been more explicit - I am in fact pushing the code to the
> remote server in such a manner that git-receive-pack is run. My

> understanding from the documentation is that this is the trigger
> which update gets called. Yet no information from that update script
> is produced in the logs or in the client.
>> 
>> As long as you only commit in your local repo nothing changes on
>> the server (remote repo), so no hook is triggered there.
>> 
>>> never occurred. I further tested the client hooks which also did
>>> not run.
>> 
>> Which ones?
>> 
>> committing locally triggers post-commit on your local repo.
> 
> These did not work.
> 
>> pushing to remote triggers post-update (and others) on the remote 
>> server's repo.
> 
> These also did not work. In short, the triggers that the
> documentation defines for both client and remote hooks fail to
> produce information in the client. Any idea on why?
> 
> Jeremiah-- To unsubscribe from this list: send the line "unsubscribe
> git" in the body of a message to majordomo@vger.kernel.org More
> majordomo info at  http://vger.kernel.org/majordomo-info.html
>