From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Named pipe problem: is this a bug?
Date: Tue, 2 Aug 2005 09:59:20 +0200 [thread overview]
Message-ID: <429BB1F8-71FA-4AE1-95D6-F6C589DDEC58@polytechnique.org> (raw)
In-Reply-To: <F0577640-623F-4147-9745-300F4303D3E6@polytechnique.org>
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
Thanks for all the answers. I tried to man and apropos fifo, but I
only have documentation about mkfifo which does not mention this issue.
Thanks again,
Alan
--
The hacker: someone who figured this out and made something cool happen.
.O.
..O
OOO
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]
prev parent reply other threads:[~2005-08-02 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 15:03 Alan Schmitt
2005-08-01 15:41 ` [Caml-list] " Virgile Prevosto
2005-08-01 15:42 ` Damien Bobillot
2005-08-01 15:55 ` Richard Jones
2005-08-02 7:59 ` Alan Schmitt [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=429BB1F8-71FA-4AE1-95D6-F6C589DDEC58@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=caml-list@inria.fr \
/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).