The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: christopher fujino <christopher.fujino@gmail.com>
To: "Greg 'groggy' Lehey" <grog@lemis.com>
Cc: UNIX Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Lions' commentary updated
Date: Wed, 27 Sep 2023 22:01:28 -0700	[thread overview]
Message-ID: <CAKP+kw-n0OxT-8DY8FMy79Dph718Lwzm-=m60RT4bPpmeg=_3w@mail.gmail.com> (raw)
In-Reply-To: <20230928040803.GC80098@eureka.lemis.com>

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

Hey Greg, thanks for sharing this!

FYI, I get a code 403 forbidden from the link:
http://www.lemis.com/grog/Documentation/Lions/book/

On Wed, Sep 27, 2023 at 9:08 PM Greg 'groggy' Lehey <grog@lemis.com> wrote:

> No, sorry, there hasn't been a new edition, just corrections.  The
> original version contained a number of scan errors, and thanks to
> Conway Yee I have now applied a number of corrections.  You can find
> the document in various forms at
> http://www.lemis.com/grog/Documentation/Lions/.
>
> I've scanned through the output, and it seems correct.  If you find
> any further errors, please let me know.
>
> Also thanks to Brian Foley, who sent me similar corrections 10 years
> ago, but which I never got round to incorporating.
>
> Greg
> --
> Sent from my desktop computer.
> Finger grog@lemis.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed.  If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA.php
>

[-- Attachment #2: Type: text/html, Size: 1677 bytes --]

  reply	other threads:[~2023-09-28  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28  4:08 [TUHS] " Greg 'groggy' Lehey
2023-09-28  5:01 ` christopher fujino [this message]
2023-09-29  4:26   ` [TUHS] " Greg 'groggy' Lehey
2023-09-29 10:01 ` rob
2023-09-29 13:52   ` Will Senn

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='CAKP+kw-n0OxT-8DY8FMy79Dph718Lwzm-=m60RT4bPpmeg=_3w@mail.gmail.com' \
    --to=christopher.fujino@gmail.com \
    --cc=grog@lemis.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).