From: Johannes Sixt <j6t@kdbg.org>
Date: Thu, 21 Apr 2016 05:15:26 GMT
Subject: Re: [PATCH 2/5] run-command: teach async threads to ignore SIGPIPE
Message-ID: <571861EE.1080202@kdbg.org>
In-Reply-To: <20160419224941.GB18255@sigill.intra.peff.net>

Am 20.04.2016 um 00:49 schrieb Jeff King:
> This is our first use of pthread_sigmask, and I think Windows will have
> to come up with something for this in compat/. I don't know how SIGPIPE
> works there at all, so it's possible that we can just turn this into a
> noop. Worst case it could probably block SIGPIPE for the whole process.

There is no SIGPIPE on Windows. write() always returns EPIPE as if 
SIGPIPE was ignored.

We'll have to make pthread_sigmask() a no-op.

-- Hannes