Johannes Schindelin 583206e958 squash! mingw: emulate write(2) that fails with a SIGPIPE
We fail with EPIPE, not SIGPIPE...

Also, replace paragraph about EINVAL on Windows by:

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.

And append:

This works around t5571.11 failing with v2.6.4.
2015-12-12 14:47:47 +01:00
2015-12-10 19:41:33 +01:00
2015-12-11 07:04:41 +01:00
2015-12-10 19:37:36 +01:00
2015-12-10 19:41:24 +01:00
2015-12-10 19:37:36 +01:00
2015-12-08 14:12:45 -08:00
2015-12-04 11:39:19 -08:00

Git for Windows

Join the chat at https://gitter.im/git-for-windows/git

This is the source code of Git for Windows, forked from Git.

This project is run by a governance model. If you encounter problems, you can report them as GitHub issues, discuss them on Git for Windows' Google Group, and contribute bug fixes.

Description
No description provided
Readme 652 MiB
Languages
C 50.5%
Shell 38.8%
Perl 4.4%
Tcl 3.2%
Python 0.8%
Other 2.1%