From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] [TUHS} 2018: eighteen months of the Unix 50th anniversary
Date: Tue, 9 Jan 2018 17:56:45 -0500 [thread overview]
Message-ID: <CAEoi9W4a790Au8cgkbHoYTzt3jbBAPX9+mRZsMRDRthJZn48yQ@mail.gmail.com> (raw)
In-Reply-To: <201801092039.w09KdVDd023506@coolidge.cs.Dartmouth.EDU>
I think that would be wonderful.
On Tue, Jan 9, 2018 at 3:39 PM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
> > I will be happy to forward pertinent suggestions.
>
> Here's one. If Bell Labs holds some kind of symposium on
> the lines of the dmr memorial, how about a plenary
> session with TV participation from remote venues (think
> Berkeley/Silicon Valley and Wollongong/Sydney--a nine-hour
> span of time zones).
>
> Any thoughts about this or other possibilities?
>
> Doug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180109/abcd3b6d/attachment.html>
next prev parent reply other threads:[~2018-01-09 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 20:39 Doug McIlroy
2018-01-09 22:56 ` Dan Cross [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-09 20:17 Doug McIlroy
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=CAEoi9W4a790Au8cgkbHoYTzt3jbBAPX9+mRZsMRDRthJZn48yQ@mail.gmail.com \
--to=crossd@gmail.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).