git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] post-receive-email hook: handle order of arguments consistently

From
APAndy Parkins <andyparkins@gmail.com>
Date
Jun 14, 2007, 10:19 UTC
Message-ID
<200706141119.18724.andyparkins@gmail.com>
In-Reply-To
<20070614090929.31616.qmail@c76df6d65db410.315fe32.mid.smarden.org>
On Thursday 2007 June 14, Gerrit Pape wrote:
> The post-receive-email hook usually gets its arguments through stdin, but
> also supports them to be specified at the command line.  The order of the
> arguments should consistently follow the documentation no matter how they
> are passed to the script.

That wasn't done casually. It was done so that the same script would work as an update hook as well.

I have no objection to the change, as the update hook was not the right place for generating emails. However, it let me use that same update hook on a system that did not have a git with support for the post-receive hook.

Andy
-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
Previous: Gerrit PapeNext: Gerrit Pape
Message 2 of 4 in “post-receive-email hook: handle order of arguments consistently”
  1. post-receive-email hook: handle order of arguments consistentlyGerrit Pape, Jun 14, 2007
  2. Andy ParkinsJun 14, 2007
  3. post-receive-email hook: handle order of arguments consistentlyGerrit Pape, Aug 7, 2007
  4. Andy ParkinsAug 7, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.