From: chet.ramey@case.edu (Chet Ramey)
Subject: [TUHS] What sparked lint? [Was: Unix stories]
Date: Thu, 5 Jan 2017 17:02:15 -0500 [thread overview]
Message-ID: <e98c4134-577b-dff7-8443-094521f073dc@case.edu> (raw)
In-Reply-To: <CAP6exY+DPbNn2psK_VdkMYZNwGNCVVJm44v0LGp99bwcpHRB8Q@mail.gmail.com>
On 1/5/17 4:42 PM, ron minnich wrote:
> the udel usenix was 1980. I was support staff :-)
I think Bill's talk was at Boulder.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet at case.edu http://cnswww.cns.cwru.edu/~chet/
prev parent reply other threads:[~2017-01-05 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 1:30 Nemo
2017-01-05 1:39 ` Larry McVoy
2017-01-05 3:20 ` Steve Johnson
2017-01-05 17:46 ` Ron Natalie
2017-01-05 20:55 ` Mary Ann Horton
2017-01-05 21:06 ` Clem Cole
2017-01-05 21:17 ` Chet Ramey
2017-01-05 21:30 ` Clem Cole
2017-01-05 21:42 ` ron minnich
2017-01-05 21:51 ` Ron Natalie
2017-01-05 22:02 ` Chet Ramey [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=e98c4134-577b-dff7-8443-094521f073dc@case.edu \
--to=chet.ramey@case.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).