From: Ken Thompson via TUHS <tuhs@minnie.tuhs.org>
To: Norman Wilson <norman@oclsc.org>
Cc: bod@usenix.org, The Eunuchs Hysterical Society <tuhs@tuhs.org>,
Stephen Jones <StephenJo@livingcomputers.org>,
AaronA@livingcomputers.org, RobertSc@livingcomputers.org
Subject: Re: [TUHS] UNIX 50th at USENIX ATC
Date: Thu, 13 Jun 2019 10:57:10 -0700 [thread overview]
Message-ID: <CAG=a+ricpx05A4mkBjHgtCduQM4z4w8jGtOsBH4vmA7_LShPcw@mail.gmail.com> (raw)
In-Reply-To: <1560278736.16251.for-standards-violators@oclsc.org>
sorry all,
i cant make it.
On Tue, Jun 11, 2019 at 11:55 AM Norman Wilson <norman@oclsc.org> wrote:
>
> Kevin Bowling:
>
> The conference looks supremely uninteresting outside one WAFL talk to me.
>
> ====
>
> That is, of course, a matter of opinion. Just from skimming
> titles I see about two dozen talks of at least some interest
> to me in the ATC program. And that's just ATC; I'm planning
> to attend the Hot* workshops on Monday and Tuesday as well.
>
> Of course I won't attend every one of those talks--some coincide
> in time, some I'll miss because I get stuck in the hallway track.
> And some will prove less interesting in practice, though others
> that don't seem all that interesting in the program will likely
> prove much better in person.
>
> I've been attending USENIX ATC for decades, and although some
> conferences have been meatier than others, I've never ended up
> feeling the trip was a waste of time.
>
> Perhaps us old farts just aren't as discriminating as you
> youngsters.
>
> That said, I think Kevin's question
>
> Is there a way to participate [on the UNIX50 event] without attending Usenix ATC?
>
> is a good one.
>
> Norman Wilson
> Toronto ON
next prev parent reply other threads:[~2019-06-13 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 18:45 Norman Wilson
2019-06-13 17:57 ` Ken Thompson via TUHS [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-09 22:32 Clem Cole
2019-06-11 17:25 ` Kevin Bowling
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='CAG=a+ricpx05A4mkBjHgtCduQM4z4w8jGtOsBH4vmA7_LShPcw@mail.gmail.com' \
--to=tuhs@minnie.tuhs.org \
--cc=AaronA@livingcomputers.org \
--cc=RobertSc@livingcomputers.org \
--cc=StephenJo@livingcomputers.org \
--cc=bod@usenix.org \
--cc=ken@google.com \
--cc=norman@oclsc.org \
--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).