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

Re: Git push failure with update hook success

From
Junio C Hamano <junkio@cox.net>
Date
Mar 8, 2007, 09:54 UTC
Message-ID
<7vvehc9i1x.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070308092809.GE30289@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 7 quoted lines
> Andy Parkins <andyparkins@gmail.com> wrote:
>> Without adding some nasty switches to git-rev-list 
>> (like --all-except-this-branch), I can't see how the post-update hook could 
>> ever send emails with the necessary amount of detail.
>
> Which is why `master` now has support for a post-receive hook,
> that has the magic three parameters.  ;-)

... but do not use that yet, as its public interface will change to take the refs parameters in different ways (and the final interface still under discussion).

Previous: Shawn O. PearceNext: Andy Parkins
Message 10 of 12 in “Git push failure with update hook success”
  1. Bill LearMar 7, 2007
  2. Bill LearMar 7, 2007
  3. Shawn O. PearceMar 7, 2007
  4. Bill LearMar 7, 2007
  5. Shawn O. PearceMar 7, 2007
  6. Shawn O. PearceMar 7, 2007
  7. Bill LearMar 7, 2007
  8. Andy ParkinsMar 8, 2007
  9. Shawn O. PearceMar 8, 2007
  10. Junio C HamanoMar 8, 2007
  11. Andy ParkinsMar 8, 2007
  12. Shawn O. PearceMar 8, 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.