| commit | 6d525d389fbef814b11e41f196e6656f2e95f412 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Fri, 5 Feb 2010 20:57:42 +0000 (5 12:57 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sat, 6 Feb 2010 04:57:27 +0000 (5 20:57 -0800) | ||
| tree | cc5ba47678e3a4177f2b9f80e1675521758e109f | treesnapshot (tar.gz zip) |
| parent | 38a81b4e82ebf57549f2fa082b329c36dffc0b18 | commitdiff |
receive-pack: Send hook output over side band #2
If the client requests to enable side-band-64k capability we can
safely send any hook stdout or stderr data down side band #2,
so the client can present it to the user.
If side-band-64k isn't enabled, hooks continue to inherit stderr
from the parent receive-pack process.
When the side band channel is being used the push client will wind up
prefixing all server messages with "remote: ", just like fetch does,
so our test vector has to be updated with the new expected output.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If the client requests to enable side-band-64k capability we can
safely send any hook stdout or stderr data down side band #2,
so the client can present it to the user.
If side-band-64k isn't enabled, hooks continue to inherit stderr
from the parent receive-pack process.
When the side band channel is being used the push client will wind up
prefixing all server messages with "remote: ", just like fetch does,
so our test vector has to be updated with the new expected output.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin-receive-pack.c | diffblobblamehistory | |
| t/t5401-update-hooks.sh | diffblobblamehistory |