From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: fifo woes
Date: Mon, 16 Jul 2012 16:37:00 -0000 [thread overview]
Message-ID: <20120716163712.GB23123@ednor.casa.cgf.cx> (raw)
In-Reply-To: <50041EEA.2020103@redhat.com>
On Mon, Jul 16, 2012 at 08:02:18AM -0600, Eric Blake wrote:
>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
You realize that your email subject gave me a nice sinking "Oh @#$*"
feeling when I saw it right? :-)
With all of the work I've put into fifos in the last couple of releases
I thought you'd found something new. It *is* nice to see Linux having
problems too. They are a lot trickier than they seem.
cgf
next prev parent reply other threads:[~2012-07-16 16:37 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
2012-07-16 16:37 ` Christopher Faylor [this message]
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=20120716163712.GB23123@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).