From: "H. Peter Anvin" <hpa@zytor.com>
To: Johannes Sixt <johannes.sixt@telecom.at>
Cc: git@vger.kernel.org
Subject: Re: MinGW port usable
Date: Wed, 31 Jan 2007 22:35:39 -0800 [thread overview]
Message-ID: <45C18A3B.2070004@zytor.com> (raw)
In-Reply-To: <200701292320.43888.johannes.sixt@telecom.at>
Johannes Sixt wrote:
>
> The README.MinGW at
> http://repo.or.cz/w/git/mingw.git?a=blob_plain;f=README.MinGW;hb=master gives
> an overview on the state. The transfer via native git protocol does not work
> and cannot be made working without major surgery(*). Theoretically, using
> netcat (nc) as GIT_PROXY_COMMAND should work, but not in my setup for some
> reason that I still do not know.
>
> (*) The reason is that on Windows read() and write() cannot operate on
> descriptors created by socket(). A work-around is to implement a (threaded)
> proxy, but that's almost the same as if netcat were used as
> GIT_PROXY_COMMAND.
>
Actually, I believe it can for the NT series kernels (at least 2000 or
later, not sure about the earlier ones), but not for the DOS-based ones.
The trick is to use _open_osfhandle() to convert the file handle (a
WinAPI construct) to a file descriptor (which in Windows is a construct
of the C library.)
In 9x/ME, a socket isn't represented by a file handle, so
_open_osfhandle() doesn't work on a socket object.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/html/_crt__open_osfhandle.asp
-hpa
next prev parent reply other threads:[~2007-02-01 6:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 22:20 MinGW port usable Johannes Sixt
2007-01-29 22:35 ` Shawn O. Pearce
2007-01-29 23:11 ` Christian MICHON
2007-01-29 23:24 ` Shawn O. Pearce
2007-01-29 23:48 ` Christian MICHON
2007-01-30 7:59 ` Christian MICHON
2007-01-30 8:07 ` Christian MICHON
2007-01-30 10:16 ` Johannes Schindelin
2007-01-30 15:27 ` Shawn O. Pearce
2007-01-30 16:31 ` Johannes Sixt
2007-01-30 8:47 ` Johannes Sixt
2007-01-29 22:46 ` Linus Torvalds
2007-01-29 23:08 ` Christian MICHON
2007-01-30 10:08 ` Johannes Schindelin
2007-01-30 10:14 ` Christian MICHON
2007-01-30 8:45 ` Johannes Sixt
2007-01-30 14:35 ` Johannes Schindelin
2007-01-30 15:18 ` Shawn O. Pearce
2007-01-30 15:38 ` Johannes Schindelin
2007-01-30 15:56 ` Shawn O. Pearce
2007-01-30 16:12 ` Johannes Schindelin
2007-01-30 16:28 ` Shawn O. Pearce
2007-01-30 16:49 ` Johannes Schindelin
2007-01-30 0:50 ` Daniel Barkalow
2007-01-30 8:23 ` Johannes Sixt
2007-01-30 8:41 ` Andreas Ericsson
2007-01-30 10:07 ` Johannes Schindelin
2007-01-30 17:09 ` Daniel Barkalow
2007-01-30 17:36 ` Johannes Schindelin
2007-01-30 18:09 ` Daniel Barkalow
2007-01-30 20:20 ` Johannes Sixt
2007-01-30 5:53 ` Junio C Hamano
2007-02-01 6:35 ` H. Peter Anvin [this message]
2007-02-01 10:34 ` Johannes Sixt
2007-02-01 21:05 ` H. Peter Anvin
2007-02-02 8:28 ` H. Peter Anvin
2007-02-02 8:49 ` Davide Libenzi
2007-02-02 8:55 ` Johannes Sixt
2007-02-02 8:55 ` H. Peter Anvin
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=45C18A3B.2070004@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.