From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Origin of the MOTD file?
Date: Thu, 15 Mar 2018 12:55:20 -0400 [thread overview]
Message-ID: <005301d3bc7e$67807790$368166b0$@ronnatalie.com> (raw)
In-Reply-To: <CAC20D2MSuHUt_1c8ne-3L7_2=jaTSs856bvVRk3o+uyDz+aj4Q@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
One of the funniest I saw was logging into a Denelcor engineering machine. Their company slogan was “Tomorrow’s computers…Today.”
I logged in to see the message “Tomorrow’s computers…some time next month.”
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180315/a418b70e/attachment.html>
next prev parent reply other threads:[~2018-03-15 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 15:29 Dan Cross
2018-03-15 15:35 ` Ron Natalie
2018-03-15 15:36 ` Chet Ramey
2018-03-15 15:41 ` Ron Natalie
2018-03-15 20:20 ` Dave Horsfall
2018-03-15 20:25 ` Warner Losh
2018-03-15 15:51 ` Clem Cole
2018-03-15 15:53 ` Clem Cole
2018-03-15 16:55 ` Ron Natalie [this message]
2018-03-15 18:04 ` Jeremy C. Reed
2018-03-15 20:00 Doug McIlroy
2018-03-15 20:51 ` Dave Horsfall
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='005301d3bc7e$67807790$368166b0$@ronnatalie.com' \
--to=ron@ronnatalie.com \
/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).