From: byron@netapp.com (Byron Rakitzis)
To: rc@hawkwind.utcs.toronto.edu
Subject: informal results
Date: Wed, 24 Mar 1993 22:50:31 -0500 [thread overview]
Message-ID: <9303250350.AA01022@netapp.netapp.com> (raw)
I received 5-6 replies to my question; some people don't use <{} at
all, some people think FIFOs are indespensible, and some would like
to see a tmp file implementation.
If I do anything about this, it will probably be to add tmp files
in addition to the two current options, though it makes me unhappy
to have 3 implementations of the same feature.
Thanks for your input,
Byron.
reply other threads:[~1993-03-25 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9303250350.AA01022@netapp.netapp.com \
--to=byron@netapp.com \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).