From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Johannes Sixt <johannes.sixt@telecom.at>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] fetch-pack: Prepare for a side-band demultiplexer in a thread.
Date: Sun, 18 Nov 2007 12:03:37 +0100 [thread overview]
Message-ID: <200711181203.37450.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <200711172309.28364.johannes.sixt@telecom.at>
lördag 17 november 2007 skrev Johannes Sixt:
> Signed-off-by: Johannes Sixt <johannes.sixt@telecom.at>
> ---
> 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.
I think this explanation deserves a place in the commit too.
-- robin
prev parent reply other threads:[~2007-11-18 11:01 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
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 [this message]
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=200711181203.37450.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.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).