From: Jeff King <peff@peff.net>
To: Stepan Kasal <kasal@ucw.cz>
Cc: GIT Mailing-list <git@vger.kernel.org>, msysgit@googlegroups.com
Subject: Re: [PATCH] tests: turn off git-daemon tests if FIFOs are not available
Date: Thu, 29 May 2014 11:57:10 -0400 [thread overview]
Message-ID: <20140529155710.GA3763@sigill.intra.peff.net> (raw)
In-Reply-To: <20140529113614.GA24293@camelia.ucw.cz>
On Thu, May 29, 2014 at 01:36:14PM +0200, Stepan Kasal wrote:
> Signed-off-by: Stepan Kasal <kasal@ucw.cz>
> ---
>
> Hi,
> mingw does not have FIFOs, so it cannot run git-daemon tests.
Thanks. I took a peek at the mkfifo call here. It is used to make sure
the daemon has started before we run the tests which depend on it. I
suspect we could do something with a regular pipe, but the code would be
rather tricky. Simply skipping the daemon tests is a reasonable
compromise until somebody feels like trying to make it work without a
fifo.
-Peff
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2014-05-29 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 11:36 [PATCH] tests: turn off git-daemon tests if FIFOs are not available Stepan Kasal
2014-05-29 15:57 ` Jeff King [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=20140529155710.GA3763@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=kasal@ucw.cz \
--cc=msysgit@googlegroups.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 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).