The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Peter Jeremy via TUHS <tuhs@minnie.tuhs.org>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Lorinda Cherry
Date: Fri, 18 Feb 2022 20:10:26 +1100	[thread overview]
Message-ID: <Yg9igohkESu815UJ@server.rulingia.com> (raw)
In-Reply-To: <BF6C9E0E30B267800D800F4DE3777C95.for-standards-violators@oclsc.org>

[-- Attachment #1: Type: text/plain, Size: 502 bytes --]

On 2022-Feb-17 22:18:25 -0500, Norman Wilson <norman@oclsc.org> wrote:
>Perhaps the best irrefutable source for Lorinda's contribution
>to dc is that cited by https://en.wikipedia.org/wiki/Lorinda_Cherry?
>
>It is, by the way, Doug's A Research UNIX Reader.  Those who
>subscribe to this list and haven't read it ought to do so; it's
>full of tidbits of history.

It was already referenced from the dc entry and I've added Lorinda
as a co-author with that as a citation.

-- 
Peter Jeremy

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply	other threads:[~2022-02-18  9:13 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  3:18 Norman Wilson
2022-02-18  9:10 ` Peter Jeremy via TUHS [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-22  0:02 Brian Walden
2022-03-01 21:51 ` Terry Jones
2022-02-15 22:31 Douglas McIlroy
2022-02-15 23:32 ` Steve Nickolas
2022-02-15 23:43   ` Jim Capp
2022-02-15 23:51     ` Larry McVoy
2022-02-16  0:54       ` Will Senn
2022-02-16  2:58         ` Steve Nickolas
2022-02-16  0:09 ` George Michaelson
2022-02-16  0:24   ` Dave Horsfall
2022-02-16  7:54     ` arnold
2022-02-16  8:13       ` markus schnalke
2022-02-16 14:54         ` Leah Neukirchen
2022-02-16 22:27           ` Dave Horsfall
2022-02-16 22:40             ` Andrew Diller
2022-02-17 10:14               ` Peter Jeremy via TUHS
2022-02-17 15:50                 ` Adam Thornton
2022-02-17 20:23                   ` Dave Horsfall
2022-02-17 10:24               ` Andy Kosela
2022-02-17 16:05                 ` Andrew Hume
2022-02-17 16:38                   ` Warner Losh
2022-02-16 22:42             ` Larry McVoy
2022-02-16 22:56               ` Clem Cole
2022-02-16 23:49                 ` Paul Winalski
2022-02-17 12:36             ` Stuart Remphrey
2022-02-17 19:59           ` Tom Ivar Helbekkmo via TUHS
2022-02-17 21:18             ` Dave Horsfall
2022-02-17 21:44               ` Bakul Shah
2022-02-18  8:33                 ` Otto Moerbeek
2022-02-22 10:39                   ` Ralph Corderoy
2022-02-22 15:53                     ` Otto Moerbeek
2022-02-20 17:29                 ` Derek Fawcus
2022-02-17 22:00               ` David Arnold
2022-02-18  9:58               ` Tom Ivar Helbekkmo via TUHS
2022-02-16 19:08   ` Diomidis Spinellis
2022-02-16 20:55     ` John P. Linderman
2022-02-16 21:17       ` Andrew Hume
2022-02-16 21:59       ` Marshall Conover
2022-02-17  5:51     ` arnold
2022-02-17 22:09     ` Will Senn
2022-02-16  0:35 ` Andrew Hume
2022-02-16  8:02 ` Thomas Paulsen
2022-02-15 21:17 John P. Linderman
2022-02-15 21:26 ` Dave Horsfall
2022-02-15 21:33 ` Jeffrey Joshua Rollin

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=Yg9igohkESu815UJ@server.rulingia.com \
    --to=tuhs@minnie.tuhs.org \
    --cc=norman@oclsc.org \
    --cc=peter@rulingia.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).