From: wlc@jctaylor.com (William Corcoran)
Subject: [TUHS] Comments in early Unix systems
Date: Wed, 21 Mar 2018 22:18:49 +0000 [thread overview]
Message-ID: <4ED5DE5D-B2FC-4018-B4A8-2639CDB2073E@jctaylor.com> (raw)
In-Reply-To: <20180321202810.GA6280@minnie.tuhs.org>
Along the same lines:
As UNIX *transitioned from the relative safety of academia (V7) into the cold, cruel corporate world (System V), was there a corresponding effort to maintain and protect the UNIX codebase into a unified master repository with SCCS, for example?
Is there any chance of finding a publicly available UNIX archive that includes the corresponding SCCS data for UNIX---to the extent that SCCS deltas and PRS comments can be examined?
Bill Corcoran
(*) IMHO
On Mar 21, 2018, at 4:28 PM, Warren Toomey <wkt at tuhs.org> wrote:
. . .
Given that the comments never made it into the compiled code, there
was no space reason to omit comments. There must have been another
reason.
Cheers, Warren
next prev parent reply other threads:[~2018-03-21 22:18 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 14:17 [TUHS] daemons are not to be exorcised Noel Chiappa
2018-03-21 15:03 ` Clem Cole
2018-03-21 16:18 ` Arthur Krewat
2018-03-21 17:28 ` Paul Winalski
2018-03-21 17:33 ` George Michaelson
2018-03-21 17:50 ` Arthur Krewat
2018-03-21 19:49 ` A. P. Garcia
2018-03-21 19:37 ` Paul Winalski
2018-03-21 17:34 ` Larry McVoy
2018-03-22 2:24 ` Dave Horsfall
2018-03-21 17:39 ` WIlliam Cheswick
2018-03-21 17:52 ` Arthur Krewat
2018-03-21 17:56 ` Nemo
2018-03-21 18:01 ` Larry McVoy
2018-03-21 18:04 ` Dan Cross
2018-03-21 19:56 ` Clem Cole
2018-03-21 20:04 ` [TUHS] comments ( was daemons exorcised ) Earl Baugh
2018-03-21 20:18 ` Paul Winalski
2018-03-21 20:51 ` Ron Natalie
2018-03-21 20:13 ` [TUHS] daemons are not to be exorcised Paul Winalski
2018-03-21 20:28 ` [TUHS] Comments in early Unix systems Warren Toomey
2018-03-21 20:48 ` Ron Natalie
2018-03-21 22:18 ` William Corcoran [this message]
2018-03-21 23:02 ` Clem Cole
2018-03-22 1:31 ` Larry McVoy
2018-03-21 23:17 ` Arthur Krewat
2018-03-21 23:50 ` Larry McVoy
2018-03-22 0:55 ` Mike Markowski
2018-03-22 1:00 ` Larry McVoy
2018-03-21 23:45 ` Warner Losh
2018-03-22 0:31 ` Steve Johnson
2018-03-22 0:58 ` Andy Kosela
2018-03-22 1:27 ` Larry McVoy
2018-03-22 1:59 ` Bakul Shah
2018-03-22 14:46 ` Steve Simon
2018-03-22 15:22 ` ron minnich
2018-03-22 16:22 ` Ron Natalie
2018-03-22 16:32 ` arnold
2018-03-22 20:20 ` Lyndon Nerenberg
2018-03-22 16:33 ` Kurt H Maier
2018-03-23 1:31 ` Charles Anthony
2018-03-22 1:40 Noel Chiappa
2018-03-22 2:19 ` Steve Nickolas
2018-03-22 13:49 Doug McIlroy
2018-03-22 14:29 ` Nemo
2018-03-23 1:54 Doug McIlroy
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=4ED5DE5D-B2FC-4018-B4A8-2639CDB2073E@jctaylor.com \
--to=wlc@jctaylor.com \
/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).