git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Sixt <johannes.sixt@telecom.at>, git@vger.kernel.org
Subject: Re: [PATCH] fetch-pack: Prepare for a side-band demultiplexer in a thread.
Date: Sun, 18 Nov 2007 02:05:32 +0100	[thread overview]
Message-ID: <20071118010532.GC7664@steel.home> (raw)
In-Reply-To: <7vtznkz8nw.fsf@gitster.siamese.dyndns.org>

Junio C Hamano, Sun, Nov 18, 2007 01:42:11 +0100:
> Johannes Sixt <johannes.sixt@telecom.at> writes:
> 
> > 	This change again originates from the MinGW port. Since we don't
> > 	have fork(2) on Windows, we must run the sideband demultiplexer
> > 	in a thread.
> 
> If the rationale was "running in a thread is more natural on the
> platform", I would understand it.
> 
> But "_must_ run because there is no fork(2)" solicits a "Huh?
> How does Cygwin does it then?" from me.
> 

You wont believe it: they start the currently running program again
and copy parents memory over into the child. Sometimes it fails.
If you want something scary:
http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fork.cc?rev=1.193&content-type=text/x-cvsweb-markup&cvsroot=src

  reply	other threads:[~2007-11-18  1:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-17 22:09 [PATCH] fetch-pack: Prepare for a side-band demultiplexer in a thread Johannes Sixt
2007-11-18  0:42 ` Junio C Hamano
2007-11-18  1:05   ` Alex Riesen [this message]
2007-11-18  9:36   ` Johannes Sixt
2007-11-18 10:16     ` Junio C Hamano
2007-11-18 12:23       ` Johannes Sixt
2007-11-18 11:03 ` Robin Rosenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071118010532.GC7664@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.sixt@telecom.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).