mirror of
https://github.com/git/git.git
synced 2026-03-13 18:33:25 +01:00
85e94b981e
Windows's _pipe() by default allocates inheritable pipes. However, when a spawn happens, we do not have a possiblility to close the unused pipe ends in the child process. This is a problem. Consider the following situation: The child process only reads from the pipe and the parent process uses only the writable end; the parent even closes the writable end. As it happens, the child at this time usually still waits for input in a read(). But since the child has inherited an open writable end, it does not get EOF and hangs ad infinitum. For this reason, pipe handles must not be inheritable. At the first glance, this is curious, since after all it is the purpose of pipes to be inherited by child processes. However, in all cases where this inheritance is needed for a file descriptor, it is dup2()'d to stdin or stdout anyway, and, lo and behold, Windows's dup2() creates inheritable duplicates.
//////////////////////////////////////////////////////////////// GIT - the stupid content tracker //////////////////////////////////////////////////////////////// "git" can mean anything, depending on your mood. - random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant. - stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang. - "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room. - "goddamn idiotic truckload of sh*t": when it breaks Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Git is an Open Source project covered by the GNU General Public License. It was originally written by Linus Torvalds with help of a group of hackers around the net. It is currently maintained by Junio C Hamano. Please read the file INSTALL for installation instructions. See Documentation/tutorial.txt to get started, then see Documentation/everyday.txt for a useful minimum set of commands, and "man git-commandname" for documentation of each command. CVS users may also want to read Documentation/cvs-migration.txt. Many Git online resources are accessible from http://git.or.cz/ including full documentation and Git related tools. The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org. To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at http://marc.theaimsgroup.com/?l=git and other archival sites.