The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Documentation for Unix 4.0
Date: Mon, 13 Jun 2022 11:49:38 -0400 (EDT)	[thread overview]
Message-ID: <8845BDF5A20243F3CD8C296C36066BB3.for-standards-violators@oclsc.org> (raw)

  Maybe make www.tuhs.org a CNAME for tuhs.org?

Surely a site devoted to the history of UNIX should use a
real link, not a symbolic one.

Norman `Old Fart' Wilson
Toronto ON

         reply	other threads:[~2022-06-13 15:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06  1:40 [TUHS] " Warren Toomey via TUHS
2022-06-06  2:15 ` [TUHS] " Warner Losh
2022-06-06  9:19   ` arnold
2022-06-06  2:26 ` Larry McVoy
2022-06-06  9:20   ` arnold
2022-06-07 16:57     ` John Cowan
2022-06-07 19:32       ` G. Branden Robinson
2022-06-09 22:19         ` Derek Fawcus
2022-06-06  6:21 ` G. Branden Robinson
2022-06-06  9:26   ` arnold
2022-06-10  6:47 ` Ed Bradford
2022-06-10  7:31   ` [TUHS] Source code for SCCS (was Re: Re: Documentation for Unix 4.0) arnold
2022-06-10  8:38     ` [TUHS] " Matthias Bruestle
2022-06-10 10:03       ` arnold
2022-06-15  5:32         ` Stuart Remphrey
2022-06-10 14:22   ` [TUHS] Re: Documentation for Unix 4.0 Clem Cole
2022-06-10 19:24     ` John Cowan
2022-06-11  4:34     ` Ed Bradford
2022-06-11 14:43       ` Clem Cole
2022-06-12  5:45         ` Ed Bradford
2022-06-12  6:41           ` Warren Toomey via TUHS
2022-06-13 13:18             ` Jay Logue via TUHS
2022-06-13 15:49               ` Norman Wilson [this message]
2022-06-13 16:39                 ` Michael Kjörling
2022-06-15  1:53                   ` Stuart Remphrey
2022-06-15  5:57                     ` Michael Kjörling
2022-06-15 12:04                       ` Dan Cross
2022-06-16  7:45                         ` Tom Ivar Helbekkmo via TUHS

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=8845BDF5A20243F3CD8C296C36066BB3.for-standards-violators@oclsc.org \
    --to=norman@oclsc.org \
    --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).