Re: Is git over http (git-http-push) ready for production ?

From: Shawn Pearce <spearce@spearce.org>
Date: Feb 19, 2010, 19:05 UTC
Message-ID: <ec874dac1002191105m6022ecdfv932a7e52eb66eb32@mail.gmail.com>
In-Reply-To: <hlm9i0$ghd$1@ger.gmane.org>

On Fri, Feb 19, 2010 at 7:08 AM, Fabien <fabien.ubuntu@gmail.com> wrote:

Show 12 quoted lines

> Ilari Liusvaara wrote:
>> 1.6.6 introduced Smart HTTP. It is much more efficient, can run hooks and
>> has same kind of atomicity guarantees as ssh://, but it has few shorcomings:
>>
>> - Requires server support (CGI script & Git 1.6.6+)
>> - Hook messages don't work (at least with 1.6.6.X/1.7.0.X)
>> - Requires 1.6.6+ on client side
>> - Authentication still sucks (no surprise, auth with HTTP just plain sucks).
>
> Ok, thanks ! I wasn't aware of this new feature.
> I'll give it a try.
> What do you mean by "Hook messages don't work" ?

Normally over ssh:// output from a hook script is sent to the client's stderr stream. This is handled by the SSH connection itself, not by Git, as SSH has two data channels from server to client (stdout, stderr). Under http:// we only have one data stream, so only the git data that normally goes over stdout gets sent to the client. The hook messages that are sent to stderr wind up in the HTTP server's error log file.

I've posted patches to multiplex these messages into the git data stream, but as far as I know, they aren't in a shipping version of Git yet.