Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Grant Taylor via COFF <coff@tuhs.org>
To: coff@tuhs.org
Subject: [COFF] Re: Will someone update the 386BSD Wikipedia page for me?
Date: Fri, 9 Sep 2022 20:26:22 -0600	[thread overview]
Message-ID: <5322d5c7-bad2-b02c-8059-8e5f8d4ac3e3@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20220910020514.GB9081@eureka.lemis.com>

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

On 9/9/22 8:05 PM, Greg 'groggy' Lehey wrote:
> Done.

Thank you!

> Do you have an idea about how this error crept in?

No, I do not.

I came to this article after reading about the DDJ DVD archive on the 
geeks mailing list.  I was sensitive to the emails about DDJ because 
I've been looking to acquire the issues (or at least articles) with the 
Porting Unix to the 386 articles in them.

Now I have them!  :-D



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4017 bytes --]

      reply	other threads:[~2022-09-10  2:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10  1:53 [COFF] " Grant Taylor via COFF
2022-09-10  2:05 ` [COFF] " Greg 'groggy' Lehey
2022-09-10  2:26   ` Grant Taylor via COFF [this message]

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=5322d5c7-bad2-b02c-8059-8e5f8d4ac3e3@spamtrap.tnetconsulting.net \
    --to=coff@tuhs.org \
    --cc=gtaylor@tnetconsulting.net \
    /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).