The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jonathan Gray <jsg@jsg.id.au>
To: Rob Pike <robpike@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Fifth Edition Manual Restoration
Date: Fri, 10 Mar 2023 18:50:51 +1100	[thread overview]
Message-ID: <ZArhW7zXWWuceaXb@largo.jsg.id.au> (raw)
In-Reply-To: <CAKzdPgxHrrL_KuwWiN0cNJJdBn3bXMEcELX7Z6uDz093ebbTfA@mail.gmail.com>

On Fri, Mar 10, 2023 at 07:48:26AM +1100, Rob Pike wrote:
> 
> Years later, bless him, Henry Spencer said something on Usenet explaining
> why the "Berkeley typesetting software" was missing the names of those who
> created it. He was in the lab that weekend and saw it happen.
> 
> -rob

https://groups.google.com/g/net.unix-wizards/c/eZ1qIlRyhx0/m/UmE8cBRYbPEJ
Henry Spencer in net.unix-wizards Dec 17, 1983

"The proper credits for vcat are roughly as follows:

Bill Reeves most of vcat, and the font editor
Tom Duff the inner loop of vcat, in pdp11 assembler
Rob Pike the (unreleased) precursor to vcat (called vd)
Mike Tilson miscellaneous optimizations

The distributed source for vcat had Reeves, Pike, Tilson in the heading,
and Duff in the lone .s file. My thanks to Rob Pike for refreshing my
memory on this."

  parent reply	other threads:[~2023-03-10  7:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  7:26 [TUHS] " segaloco via TUHS
2023-03-08 10:02 ` [TUHS] " Angelo Papenhoff
2023-03-08 16:02   ` segaloco via TUHS
2023-03-08 16:30     ` Angelo Papenhoff
2023-03-08 20:55       ` josh
2023-03-08 22:21         ` segaloco via TUHS
2023-03-08 23:09       ` David Arnold
2023-03-09  6:59         ` arnold
2023-03-09 14:24         ` Clem Cole
2023-03-09 20:48           ` Rob Pike
2023-03-09 21:04             ` Dave Horsfall
2023-03-09 22:32             ` Rich Salz
2023-03-09 23:51             ` Jeremy C. Reed
2023-03-10  1:58               ` Rob Pike
2023-03-10  6:33               ` Jonathan Gray
2023-03-10  7:50             ` Jonathan Gray [this message]
2023-03-10 13:11               ` Clem Cole

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=ZArhW7zXWWuceaXb@largo.jsg.id.au \
    --to=jsg@jsg.id.au \
    --cc=robpike@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).