From: Eric Blake <eblake@redhat.com>
Cc: fifos are tough <cygwin-talk@cygwin.com>
Subject: Re: fifo woes
Date: Mon, 16 Jul 2012 14:02:00 -0000 [thread overview]
Message-ID: <50041EEA.2020103@redhat.com> (raw)
In-Reply-To: <50041EA9.4020102@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
On 07/16/2012 08:01 AM, Eric Blake wrote:
> It's nice to know that Cygwin isn't the only platform plagued with fifo
> woes; here's a bug in the Linux kernel handling of fifos that manifested
> itself when dash was used to run the git testsuite:
>
> http://news.gmane.org/gmane.comp.shells.dash
It helps if I post the right link:
http://thread.gmane.org/gmane.comp.shells.dash/745/focus=763
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2012-07-16 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 14:01 Eric Blake
2012-07-16 14:02 ` Eric Blake [this message]
2012-07-16 16:37 ` Christopher Faylor
2012-07-16 17:01 ` Corinna Vinschen
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=50041EEA.2020103@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin-talk@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).