On 3/25/13 19:31 , Rom Walton wrote: > 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.
That's what I wanted to know. So it's like I thought. I still consider this bad design as it seems to invite race conditions. The question is: does anyone need "dumb" HTTP-based access? It's only useful if someone isn't allowed to access port 9418 of the git daemon - which is hardly an issue for outbound connections... Your call. 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.
