{"thread":{"id":"12084","subject":"[PATCH RESEND 0/6] Sideband support in push (send-pack/receive-pack)","startedAt":"2008-02-14T06:22:02Z","lastAt":"2008-02-14T06:22:02Z","messageCount":1,"participants":["Shawn O. Pearce"],"isPatch":true,"patchVersion":1,"patchTotal":6},"messages":[{"id":"68706","messageId":"20080214062202.GI24004@spearce.org","threadId":"12084","inReplyTo":null,"subject":"[PATCH RESEND 0/6] Sideband support in push (send-pack/receive-pack)","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-02-14T06:22:02Z","receivedAt":"2008-02-14T06:22:02Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"This series adds the same sort of sideband channel we use in fetch\n(fetch-pack/upload-pack) to pass progress messages back to the\nclient from the server side.\n\n  1)  Allow run_command stdout_to_stderr when stderr is a pipe\n  2)  Automatically close stderr pipes created by run_command\n  3)  Refactor packet_write to prepare to integrate with sideband\n  4)  Refactor send-pack/receive-pack capability handshake for extension\n  5)  Add side-band-64k extension to send-pack/receive-pack for hook output\n  6)  Redirect receive-pack hook output into sideband channel\n\nI didn't really see any comments from the list on this topic the\nlast time I posted it for comment, so here is a rebased version\non current master.\n\n-- \nShawn.\n"}]}