From: Pete Wright via TUHS <tuhs@tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Nice video with Brian Kernighan
Date: Thu, 18 Aug 2022 15:48:44 -0700 [thread overview]
Message-ID: <9e060307-6c7e-1ea3-7926-01a1cb047d58@nomadlogic.org> (raw)
In-Reply-To: <CAC20D2Nt_U52Sk8z_wt9ckNvjw6CFCSLJff7Hj3pwF=T-48DFw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
On 8/18/22 14:58, Clem Cole wrote:
> Thanks Arnold -- always fun.
agreed! i shared this with my data engineering team - i hope historical
context like this helps them in how they approach their data processing
tasks.
-pete
--
Pete Wright
pete@nomadlogic.org
@nomadlogicLA
[-- Attachment #2: Type: text/html, Size: 985 bytes --]
next prev parent reply other threads:[~2022-08-18 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 10:01 [TUHS] " Arnold Robbins
2022-08-18 21:58 ` [TUHS] " Clem Cole
2022-08-18 22:48 ` Pete Wright via TUHS [this message]
2022-08-20 15:48 Douglas McIlroy
2022-08-20 16:17 ` Clem Cole
2022-08-20 18:24 ` Rich Morin
2022-08-21 15:09 ` John Cowan
2022-08-21 15:41 ` Clem Cole
2022-08-22 2:49 ` John Cowan
2022-08-21 20:07 ` Rich Morin
2022-08-21 9:36 ` Mohamed Akram
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=9e060307-6c7e-1ea3-7926-01a1cb047d58@nomadlogic.org \
--to=tuhs@tuhs.org \
--cc=pete@nomadlogic.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).