-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nathaniel Smith wrote:
A third possibility is that there are issues with the
talk-to-child-process code on windows, which is utterly nasty. It
took ages and ages to get that code working at all, it's still
very difficult to understand, and there are still intermittent
failures in the test suite that no-one has managed to reliably
reproduce, where it just blocks forever waiting on the child
process... (our best guess so far is that it might have something to
do with windows having a broken buffering model for named pipes).
There is a identical (as far as this description goes) bug with
rsync-over-ssh on Cygwin, that most people blame on Cygwin's spawning
code: that's why I was asking which SSH was in use exactly, it
would be
partly a relief to know that it is Windows's fault, and not
Cygwin's ;-)