From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
To: "Dan Cross" <crossd@gmail.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Unix 50 event at BTL Murray Hill?
Date: Mon, 14 Oct 2019 14:22:47 +0200 [thread overview]
Message-ID: <eb6fa9ee9cdb27580df5c190ff4d725d@firemail.de> (raw)
In-Reply-To: <CAEoi9W7Bt+fiKDWL9bF2krqpixZioNzxUwYyhHDPUPMeA0dQbg@mail.gmail.com>
isn't late October somewhat too late as Ken did his work in summer '69.
--- Ursprüngliche Nachricht ---
Von: Dan Cross <crossd@gmail.com>
Datum: 14.10.2019 13:57:14
An: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Betreff: [TUHS] Unix 50 event at BTL Murray Hill?
> This just came over another list, and I'm surprised not to have seen
> anything about it here. Anyone heard about it?
>
> https://tech.slashdot.org/story/19/10/12/1625237/bell-labs-plans-big-50th-anniversary-event-for-unix
>
>
> - Dan C.
>
prev parent reply other threads:[~2019-10-14 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 11:57 Dan Cross
2019-10-14 12:22 ` Thomas Paulsen [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=eb6fa9ee9cdb27580df5c190ff4d725d@firemail.de \
--to=thomas.paulsen@firemail.de \
--cc=crossd@gmail.com \
--cc=tuhs@tuhs.org \
/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).