Re: [PATCH] hook: introduce the report hook for git-receive-pack(1)

Phillip Wood [off-list ref] writes:

I think the question the commit message should be answering is, whether 
a design like proc-receive that predates config based hooks and only 
allows a single hook script, makes sense now that we have config based 
hooks, or, if we were adding that functionality now, would we design it 
differently?

Yeah, I think it is a reasonable way to frame the problem.

I think the answer for server side hooks is that a design 
around a single script is probably reasonable but it would be worth 
discussing that in the commit message.

Hmph, I am not sure what the hook being on the server side has to
do with the design decision to accept the limitation of allowing
only one hook script.  It is not as if a single entity has tighter
control on the server than on the end-user desktop repository,
making it easier to live with such a limitation on the server side.