From: "Torsten Bögershausen" <tboegi@web.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Mark Levedahl <mlevedahl@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] test-lib.sh - cygwin does not have usable FIFOs
Date: Sun, 07 Jul 2013 11:14:12 +0200 [thread overview]
Message-ID: <51D93164.8030202@web.de> (raw)
In-Reply-To: <20130707005558.GI30132@google.com>
On 2013-07-07 02.55, Jonathan Nieder wrote:
> Mark Levedahl wrote:
>
>> Do not use FIFOs on cygwin, they do not work. Cygwin includes
>> coreutils, so has mkfifo, and that command does something. However,
>> the resultant named pipe is known (on the Cygwin mailing list at
>> least) to not work correctly.
>
> Hm. How would you recommend going about writing a script that takes
> output from a command, transforms it, and then feeds it back into
> that command's input? Are sockets a more reliable way to do this kind
> of IPC on Cygwin?
>
> See reinit_git and try_dump from t9010-svn-fe.sh for context.
>
> Thanks,
> Jonathan
t9010 needs PIPE in most test cases as a prerequisite.
And if PIPE isn't available, the tests can not be run.
Are you suggesting to replace the named pipes with a TCP socket?
Disabling PIPE under cygwin seems to be the right thing to do,
or do I miss something ?
/Torsten
next prev parent reply other threads:[~2013-07-07 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 22:04 [PATCH] test-lib.sh - cygwin does not have usable FIFOs Mark Levedahl
2013-07-07 0:55 ` Jonathan Nieder
2013-07-07 9:14 ` Torsten Bögershausen [this message]
2013-07-14 0:59 ` Jonathan Nieder
2013-07-08 22:18 ` Mark Levedahl
2013-07-14 0:57 ` Jonathan Nieder
2013-07-14 15:38 ` Mark Levedahl
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=51D93164.8030202@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mlevedahl@gmail.com \
/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.