diff options
| author |  Shawn O. Pearce <spearce@spearce.org> | 2010-02-05 12:57:42 -0800 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2010-02-05 20:57:27 -0800 |
| commit | 6d525d389fbef814b11e41f196e6656f2e95f412 (patch) | |
| tree | cc5ba47678e3a4177f2b9f80e1675521758e109f /t/t5515/fetch.br-unconfig_branches-default | |
| parent | receive-pack: Wrap status reports inside side-band-64k (diff) | |
| download | tgif-6d525d389fbef814b11e41f196e6656f2e95f412.tar.xz | |
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>
Diffstat (limited to 't/t5515/fetch.br-unconfig_branches-default')
0 files changed, 0 insertions, 0 deletions