From: Will Senn <will.senn@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 211BSD Version in the Unix Archive
Date: Mon, 20 Jul 2020 12:06:39 -0500 [thread overview]
Message-ID: <c75294ed-fe55-bb7e-68ff-f8d8a897e763@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
Well, I figured out number 4, duh!
4. Is there a howto bring it up to the next patch level document lying
around somewhere?
Each patch is self documenting :). Just do what it says and it should
work... we'll see!
Will
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
[-- Attachment #2: Type: text/html, Size: 618 bytes --]
next reply other threads:[~2020-07-20 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:06 Will Senn [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-20 16:45 Will Senn
2020-07-20 17:49 ` Warner Losh
2020-07-20 18:03 ` 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=c75294ed-fe55-bb7e-68ff-f8d8a897e763@gmail.com \
--to=will.senn@gmail.com \
--cc=tuhs@minnie.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).