From: Johannes Schindelin Date: Thu, 17 Dec 2015 17:08:15 +0000 (+0100) Subject: mingw: emulate write(2) that fails with a EPIPE X-Git-Tag: v2.7.0-rc2~1^2 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/2b86292ed1756a66439f79ceda88dfc86a10dfa9?hp=2b86292ed1756a66439f79ceda88dfc86a10dfa9 mingw: emulate write(2) that fails with a EPIPE On Windows, when writing to a pipe fails, errno is always EINVAL. However, Git expects it to be EPIPE. According to the documentation, there are two cases in which write() triggers EINVAL: the buffer is NULL, or the length is odd but the mode is 16-bit Unicode (the broken pipe is not mentioned as possible cause). Git never sets the file mode to anything but binary, therefore we know that errno should actually be EPIPE if it is EINVAL and the buffer is not NULL. See https://msdn.microsoft.com/en-us/library/1570wh78.aspx for more details. This works around t5571.11 failing with v2.6.4 on Windows. Signed-off-by: Johannes Schindelin Acked-by: Johannes Sixt Signed-off-by: Junio C Hamano ---