From: "Boyd Roberts" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] to-do list for plan 9
Date: Wed, 30 Apr 2003 02:41:44 +0200 [thread overview]
Message-ID: <00d601c30eb1$466c2a80$e3944251@insultant.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0304291826540.8254-100000@maxroach.lanl.gov>
yeah i was at PRL, i ran that lab as a sysadmin. it was nice :)
although the syntax was horrible, but it was a cool thing ...
prev parent reply other threads:[~2003-04-30 0:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 21:58 Fco.J.Ballesteros
2003-04-29 14:49 ` ron minnich
2003-04-29 14:55 ` Russ Cox
2003-04-29 16:29 ` Christopher Nielsen
2003-04-29 15:39 ` Sam
2003-04-29 15:56 ` andrey mirtchovski
2003-04-29 16:12 ` ron minnich
2003-04-29 16:35 ` Christopher Nielsen
2003-04-30 7:58 ` Fco.J.Ballesteros
2003-04-29 16:28 ` Christopher Nielsen
2003-04-29 16:26 ` Christopher Nielsen
2003-04-30 0:02 ` Boyd Roberts
2003-04-30 0:26 ` ron minnich
2003-04-30 0:41 ` Boyd Roberts [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='00d601c30eb1$466c2a80$e3944251@insultant.net' \
--to=boyd@insultant.net \
--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).