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

Re: git-http-backend: hook output not delivered to client

From
Shawn O. Pearce <spearce@spearce.org>
Date
Mar 6, 2010, 22:30 UTC
Message-ID
<20100306223031.GG2529@spearce.org>
In-Reply-To
<3C07BFC0-BC5E-4901-A846-A337B5F1B8F4@bjhargrave.com>
BJ Hargrave <bj@bjhargrave.com> wrote:
> I have compiled and installed git 1.7.0.1 on a RHEL4 box
... 
> So the push properly fails in both cases because the hook exits
> with a non-zero return code, but it seems there is a problem with
> git-http-backend not ferrying the hook output messages back to
> the client.
Yes, we know about this problem.

You need commit 466dbc42f5 ("receive-pack: Send internal errors over side-band #2") on both the client and the server for hook messages to work over HTTP.

This hasnt been released yet.  It is slated for 1.7.0.2.
-- 
Shawn.
Previous: BJ HargraveNext: BJ Hargrave
Message 2 of 3 in “git-http-backend: hook output not delivered to client”
  1. BJ HargraveMar 6, 2010
  2. Shawn O. PearceMar 6, 2010
  3. BJ HargraveMar 6, 2010

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.