From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs upgrade
Date: Tue, 6 Nov 2001 11:53:30 -0500 [thread overview]
Message-ID: <200111061653.LAA09073@augusta.math.psu.edu> (raw)
In-Reply-To: <20011106070855.6A0ED199B5@mail.cse.psu.edu>
In article <20011106070855.6A0ED199B5@mail.cse.psu.edu> you write:
>If forsyth finds out where he had the code to grow I'm willing to
>merge it into the ide patch for the fs kernel. At least, that
>would let us grow before something better gets integrated (?)
>into the official fs code.
Cool, thanks Nemo. btw- on a related note, can anyone at the labs
comment on how the recent economic situation has affected the various
fileserver work currently in progress? Is there anything that the
community can do to help out?
- Dan C.
next prev parent reply other threads:[~2001-11-06 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 7:08 Fco.J.Ballesteros
2001-11-06 16:53 ` Dan Cross [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-09 18:20 jmk
2001-11-05 17:12 forsyth
2001-11-05 16:26 Russ Cox
2001-11-05 10:27 Fco.J.Ballesteros
2001-11-05 10:25 forsyth
2001-11-05 20:03 ` Dan Cross
2001-11-05 7:34 Fco.J.Ballesteros
2001-11-04 19:48 anothy
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=200111061653.LAA09073@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).