From: "Shawn O. Pearce" <spearce@spearce.org>
To: BJ Hargrave <bj@bjhargrave.com>
Cc: git@vger.kernel.org
Subject: Re: git-http-backend: hook output not delivered to client
Date: Sat, 6 Mar 2010 14:30:31 -0800 [thread overview]
Message-ID: <20100306223031.GG2529@spearce.org> (raw)
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.
next prev parent reply other threads:[~2010-03-06 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 22:24 git-http-backend: hook output not delivered to client BJ Hargrave
2010-03-06 22:30 ` Shawn O. Pearce [this message]
2010-03-06 22:53 ` BJ Hargrave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100306223031.GG2529@spearce.org \
--to=spearce@spearce.org \
--cc=bj@bjhargrave.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).