dc364ab06b
On Windows 7 and older, the API to restrict which file handles get to be inherited by a spawned process is a bit peculiar. For example, when launching `git ls-remote https://...` in a Git Bash, everything works as expected. But when launching that in a Git CMD, CreateProcessW() will fail (with an ERROR_NO_SYSTEM_RESOURCES) if even one of the standard handles are marked to be inherited specifically. Apparently, it has something to do with handles' file types and with cmd.exe setting up its standard handles in a specific way. Rather than trying to guess correctly under which circumstances we should, or should not, list those standard handles, let's just work around this by detecting that particular error and simply trying to call CreateProcessW() again, this time without any special thread attribute list to restrict which handles get to be inherited by the spawned process. This means that we potentially run into more locking problems on Windows 7 and older than we would like, but it is still better than to deny Git to spawn any child processes. This fixes https://github.com/git-for-windows/git/issues/1475 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Git for Windows
This is Git for Windows, the Windows port of Git.
The Git for Windows project is run using 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.
Git - fast, scalable, distributed revision control system
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 version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.
Please read the file INSTALL for installation instructions.
Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.
See Documentation/gittutorial.txt to get started, then see
Documentation/giteveryday.txt for a useful minimum set of commands, and
Documentation/git-.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with man gittutorial or git help tutorial, and the
documentation of each command with man git-<commandname> or git help <commandname>.
CVS users may also want to read Documentation/gitcvs-migration.txt
(man gitcvs-migration or git help cvs-migration if git is
installed).
The user discussion and development of core 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 (read Documentation/SubmittingPatches for instructions on patch submission). 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 https://public-inbox.org/git/, http://marc.info/?l=git and other archival sites. The core git mailing list is plain text (no HTML!).
The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.
The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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