Johannes Sixt 75301f9015 Windows: avoid the "dup dance" when spawning a child process
When stdin, stdout, or stderr must be redirected for a child process that
on Windows is spawned using one of the spawn() functions of Microsoft's
C runtime, then there is no choice other than to

1. make a backup copy of fd 0,1,2 with dup
2. dup2 the redirection source fd into 0,1,2
3. spawn
4. dup2 the backup back into 0,1,2
5. close the backup copy and the redirection source

We used this idiom as well -- but we are not using the spawn() functions
anymore!

Instead, we have our own implementation. We had hardcoded that stdin,
stdout, and stderr of the child process were inherited from the parent's
fds 0, 1, and 2. But we can actually specify any fd.

With this patch, the fds to inherit are passed from start_command()'s
WIN32 section to our spawn implementation. This way, we can avoid the
backup copies of the fds.

The backup copies were a bug waiting to surface: The OS handles underlying
the dup()ed fds were inherited by the child process (but were not
associated with a file descriptor in the child). Consequently, the file or
pipe represented by the OS handle remained open even after the backup copy
was closed in the parent process until the child exited.

Since our implementation of pipe() creates non-inheritable OS handles, we
still dup() file descriptors in start_command() because dup() happens to
create inheritable duplicates. (A nice side effect is that the fd cleanup
in start_command is the same for Windows and Unix and remains unchanged.)

Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-01-16 16:43:53 -08:00
2010-01-12 13:18:27 -08:00
2009-12-09 15:38:51 -08:00
2010-01-13 12:31:13 -08:00
2010-01-13 12:30:39 -08:00
2009-09-14 02:23:36 -07:00
2009-06-30 16:12:24 -07:00
2009-04-17 21:05:49 -07:00
2010-01-10 00:51:54 -08:00
2010-01-13 11:58:34 -08:00
2010-01-13 12:30:39 -08:00
2009-12-22 12:32:39 -08:00
2010-01-13 11:58:34 -08:00
2009-12-26 14:03:16 -08:00
2010-01-13 11:58:34 -08:00
2008-08-28 20:50:10 -07:00
2009-12-26 14:03:16 -08:00
2009-12-03 10:08:54 -08:00
2010-01-13 11:58:34 -08:00
2009-08-05 12:39:33 -07:00
2010-01-13 11:58:34 -08:00
2009-11-23 21:54:39 -08:00
2010-01-13 11:58:34 -08:00
2009-12-05 11:39:13 -08:00
2010-01-13 11:58:56 -08:00
2009-11-23 21:54:39 -08:00
2009-08-07 22:35:17 -07:00
2009-11-23 22:30:08 -08:00
2010-01-13 12:31:13 -08:00
2009-02-13 17:27:58 -08:00
2009-11-20 23:53:55 -08:00
2009-11-20 23:51:23 -08:00
2010-01-13 11:58:34 -08:00
2009-12-26 14:03:16 -08:00
2009-11-23 22:24:01 -08:00
2009-09-13 01:32:26 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -07:00
2009-10-03 06:04:38 -04:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2010-01-13 11:58:34 -08:00
2010-01-13 11:58:34 -08:00
2008-11-02 16:36:40 -08:00
2010-01-13 11:58:34 -08:00
2010-01-13 11:58:34 -08:00
2010-01-13 11:58:34 -08:00
2010-01-13 11:58:34 -08:00
2009-12-08 22:47:09 -08:00
2009-12-13 23:40:24 -08:00
2009-12-08 22:47:09 -08:00
2009-12-26 14:11:46 -08:00
2009-11-23 22:24:01 -08:00
2008-09-07 23:52:16 -07:00
2010-01-10 08:53:04 -08:00
2009-11-04 17:58:15 -08:00
2009-11-13 12:16:30 -08:00
2009-11-22 16:28:14 -08:00
2009-04-22 19:02:12 -07:00
2010-01-16 16:43:49 -08:00
2008-10-25 12:09:31 -07:00
2009-08-21 18:47:53 -07:00
2009-08-21 18:47:53 -07:00
2009-11-30 14:44:22 -08:00
2010-01-13 11:58:56 -08:00
2009-12-26 14:20:09 -08:00
2010-01-12 15:48:38 -08:00
2009-12-26 14:03:16 -08:00
2009-12-26 14:03:16 -08:00
2009-02-14 21:27:35 -08:00
2009-11-23 22:30:08 -08:00
2009-11-04 17:58:15 -08:00
2010-01-10 08:52:10 -08:00
2009-11-04 17:58:15 -08:00
2009-01-17 18:30:41 -08:00
2009-08-30 22:04:46 -07:00
2009-08-23 17:11:28 -07:00
2009-04-20 13:44:14 -07:00
2010-01-13 11:58:56 -08:00
2009-12-10 16:20:59 -08:00
2009-11-22 16:14:48 -08:00
2009-11-13 12:20:47 -08:00
2009-07-22 21:57:41 -07:00
2009-12-27 23:01:32 -08:00

////////////////////////////////////////////////////////////////

	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/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.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).

Many Git online resources are accessible from http://git-scm.com/
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.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%