From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] Re: 9p & read-ahead
Date: Thu, 31 Jul 2003 06:27:24 -0500 [thread overview]
Message-ID: <Pine.LNX.4.33.0307310626500.15683-100000@einstein.ssz.com> (raw)
In-Reply-To: <28cbe19e5474cf6db7ca08daae97e949@yourdomain.dom>
On Thu, 31 Jul 2003 steve.simon@snellwilcox.com wrote:
> Anyone any strong views about this?
Add a switch so that anyone who does in a negative way can turn it off.
--
____________________________________________________________________
We are all interested in the future for that is where you and I
are going to spend the rest of our lives.
Criswell, "Plan 9 from Outer Space"
ravage@ssz.com jchoate@open-forge.org
www.ssz.com www.open-forge.org
--------------------------------------------------------------------
next prev parent reply other threads:[~2003-07-31 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 8:29 [9fans] " steve.simon
2003-07-31 8:37 ` boyd, rounin
2003-07-31 9:44 ` Bruce Ellis
2003-07-31 9:50 ` boyd, rounin
2003-07-31 20:52 ` rog
2003-07-31 11:27 ` Jim Choate [this message]
2003-07-31 15:07 ` [9fans] " splite
2003-07-31 16:04 ` Jack Johnson
2003-07-31 23:36 ` [9fans] " Geoff Collyer
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=Pine.LNX.4.33.0307310626500.15683-100000@einstein.ssz.com \
--to=ravage@einstein.ssz.com \
--cc=9fans@cse.psu.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).