To: email@example.com, firstname.lastname@example.org
Subject: Re: [TUHS] Brenda Baker's Struct Memo
Date: Thu, 03 Mar 2022 03:22:43 -0700 [thread overview]
Message-ID: <202203031022.223AMh5E019690@freefriends.org> (raw)
I have added this to the Git repo. Doug and Warren, much thanks!
Warren Toomey <email@example.com> wrote:
> All, I've just placed this document at
> Many thanks to Doug for passing it on!
> Cheers, Warren
> ----- Forwarded message from Douglas McIlroy -----
> Someone asked if Brenda Baker's original technical memorandum about
> struct is available. I scanned my copy and passed it on, secure in my
> belief that the Labs won't care since it is essentially the same as
> her journal publication.
> For the memo to be genuinely available, I'd like to send it to TUHS.
> With that in mind I redacted information about corporate organization
> and distribution channels. However the memo still bears the AT&T logo
> and the words "not for publication".
> ----- End forwarded message -----
next prev parent reply other threads:[~2022-03-03 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 21:18 Warren Toomey
2022-03-03 10:22 ` arnold [this message]
2022-03-02 21:44 Nelson H. F. Beebe
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).