Per:
https://www.kernel.org/pub/software/scm/git/docs/githooks.html

post-update

This hook is invoked by git-receive-pack on the remote repository, which
happens when a git push is done on a local repository. It executes on
the remote repository once after all the refs have been updated.

It takes a variable number of parameters, each of which is the name of
ref that was actually updated.

This hook is meant primarily for notification, and cannot affect the
outcome of git-receive-pack.

The post-update hook can tell what are the heads that were pushed, but
it does not know what their original and updated values are, so it is a
poor place to do log old..new. The post-receive hook does get both
original and updated values of the refs. You might consider it instead
if you need them.

When enabled, the default post-update hook runs git update-server-info
to keep the information used by dumb transports (e.g., HTTP) up-to-date.
If you are publishing a git repository that is accessible via HTTP, you
should probably enable this hook.

Both standard output and standard error output are forwarded to git
send-pack on the other end, so you can simply echo messages for the
user.

----- Rom

-----Original Message-----
From: Oliver Bock [mailto:[email protected]] 
Sent: Monday, March 25, 2013 2:27 PM
To: Rom Walton
Cc: Gianfranco Costamagna; [email protected]; Boinc
Subject: Re: [boinc_alpha] [boinc_dev] boinc-v2 broken?

Hi Rom,

On 3/25/13 19:11 , Rom Walton wrote:
> I forgot about the post-update hook.
> 
> I have manually executed it and set it up to run after every commit.
> It is what keeps the git-upload-pack/git-download-pack files 
> up-to-date.

Can you elaborate on this? What's the purpose of these specific hooks?
This sounds like bad design. Are these used just to allow for the http
downloads...?

Cheers,
Oliver
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to