On Sun, Aug 17, 2014 at 8:14 PM, Eric Wong [off-list ref] wrote:
But unicorn would ignore SIGPIPE it if Ruby did not; relying on SIGPIPE
while doing any multiplexed I/O doesn't work well.
Exactly. Callers block SIGPIPE for their own legitimate reasons, but they
don't consistently unblock it before spawning a git subprocess that needs
the default SIGPIPE behavior. Easier to fix it in git than in every potential
caller.
--Patrick