On Apr 26, 2010, at 8:11 PM, Jacob Helwig wrote: > On Mon, Apr 26, 2010 at 11:04, Jeremiah Foster >> >> >> Can I confirm that hooks work with this type of transport? > > The real problem is that you're using a post-commit hook (or at least > everything you said in your original email implies you are). > post-commit hooks are only triggered in your _local_ repository, since > this is the only place you actually commit. Doesn't matter which > transport you're using, post-commit will never be triggered by a push. > > 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 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 never occurred. I further tested the client hooks which also did not run. I wonder if git is not seeing the scripts or if the backend mechanism has changed in some manner from one version of git to another? Any insight is welcome. I'll run the hooks in the client with strace to see if I can get any information on what is happening. Jeremiah-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html