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

Re: Git push failure with update hook success

From
Shawn O. Pearce <spearce@spearce.org>
Date
Mar 7, 2007, 23:09 UTC
Message-ID
<20070307230948.GE27922@spearce.org>
In-Reply-To
<17902.62836.920473.810183@lisa.zopyra.com>
Bill Lear <rael@zopyra.com> wrote:
Show 6 quoted lines
> Since it just gets the ref name, would one (of sufficient skill) be
> able to reconstruct the same sort of report that the "pre" update hook
> does?  That is, from the ref name can I get the old SHA-1?  If I try
> to write this, what I think I would like to do is just call the
> existing update hook from the post-update hook, with the post update
> hook figuring out the proper arguments to pass along.

For what its worth, the receive-pack patch series that I posted a few hours ago creates a new post-receive hook that would be suitable for generating the report you are looking for.

-- 
Shawn.
Previous: Shawn O. PearceNext: Bill Lear
Message 6 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.