The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Brad Spencer <brad@anduin.eldar.org>
To: segaloco <segaloco@protonmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Mon, 19 Dec 2022 19:02:24 -0500	[thread overview]
Message-ID: <xonr0wvndrj.fsf@anduin.eldar.org> (raw)
In-Reply-To: <N7OY44B9opZ4dPSe_0Qqq2Xo-Y8f4JUFFsSUuj2P0ytguvneHxqTwViqi-15_STEUU650pt2LKKbVwfEbDQuFzh3p5x6ZzQ99PZQ7KV36IQ=@protonmail.com> (message from segaloco via TUHS on Mon, 19 Dec 2022 22:15:29 +0000)

segaloco via TUHS <tuhs@tuhs.org> writes:

[snip]

> Another matter I've been keeping tabs on in my recent study is the presence of SCCS tags on things. Most System V code has SCCS tags, but only select bits of System III seem to have them. Where they do exist, often times they're either carried through to the System V file verbatim or​ there's some monkeying with the numbers I can't quite explain but I have some hunches. In any case, many of the files unmodified between III and V are listed as SCCS version 1.1 in V. I'm not sure there what the significance of the version numbers was, and in analyzing several versions, i haven't been able to identify a singular pattern. One pattern I did notice sporadically was when comparing SVR1 Release 1 (PDP-11) and SVR1 Release 2 (M68K), all of these SCCS identifiers I checked roll from whatever 1.x they were in the former to 2.1 in the latter, presumably the major number being the System V release and minor being revisions since that was tagged? All speculation though.

[snip]

Someone else will have to indicate if raw SCCS was used during the time
frame for the code you are looking at or if there was some management
system built on SCCS that was actually used.

What I mean by this is that there was a source code control management
system used at AT&T and later Lucent called Sublime (it was more or less
mandated at CB at least for the software groups I know of and I am
pretty sure I remember it in other locations too).  Sublime was used in
the '90s onward and likely quite a bit before that time.  This system
was a layer on top of SCCS, which wasn't allowed to be used directly for
source code control.  It was true that SCCS tags ended up in your code
(usually), but you could not directly use the tag information in any
meaningful manor.  Sublime used the tag information in it own way that
was opaque to the software developers.





-- 
Brad Spencer - brad@anduin.eldar.org - KC8VKS - http://anduin.eldar.org

  reply	other threads:[~2022-12-20  0:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 17:38 [TUHS] " Phil Budne
2022-12-19 18:53 ` [TUHS] " segaloco via TUHS
2022-12-19 21:01   ` Clem Cole
2022-12-19 21:19     ` Rob Pike
2022-12-19 22:15       ` segaloco via TUHS
2022-12-20  0:02         ` Brad Spencer [this message]
2022-12-20  1:04           ` Adam Thornton
2022-12-20  2:35             ` segaloco via TUHS
2022-12-20 14:25           ` Andrew Hume
2022-12-19 23:02       ` Clem Cole
2022-12-20  1:20         ` Larry Stewart
2022-12-20  1:33           ` Larry McVoy
2022-12-20  1:57             ` George Michaelson
2022-12-20  2:06               ` Dan Cross
2022-12-20 15:04                 ` Chet Ramey
2022-12-20  2:12               ` Adam Thornton
2022-12-20 15:29                 ` Andy Kosela
2022-12-20 15:35                   ` Adam Thornton
2022-12-21  2:43                     ` Luther Johnson
2022-12-20 23:18                 ` David Arnold
2022-12-20  2:52       ` Bakul Shah
2022-12-20  3:09         ` Larry McVoy
2022-12-20  3:27           ` Bakul Shah
2022-12-20  3:48           ` Warner Losh
2022-12-20  4:21           ` Jonathan Gray
2022-12-19 21:36 ` Marc Donner
2022-12-19 22:52   ` Charles H Sauer (he/him)
     [not found]   ` <01428a75-3507-7b8a-fd35-cef74c8c0bd2@ucsb.edu>
2022-12-20  1:49     ` [TUHS] Re: pre-1991 USENIX proceedings Marc Donner
2022-12-20  3:11 ` [TUHS] Re: UNIX on (not quite bare) System/370 Warner Losh
2022-12-20  8:56 ` arnold
2022-12-20  9:31   ` segaloco via TUHS
2022-12-20  9:39     ` arnold
2022-12-20  9:55       ` Jonathan Gray
2022-12-20 14:27     ` Clem Cole
2022-12-23  1:53       ` Rob Gingell
2022-12-22 19:00 ` Andrew Hume
2022-12-20 22:25 Noel Chiappa
2022-12-20 23:18 ` Bakul Shah
2022-12-22 17:26 Noel Chiappa
2022-12-22 17:33 ` Dan Cross
2022-12-22 20:25 ` Warner Losh
2022-12-22 23:06   ` Warner Losh

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=xonr0wvndrj.fsf@anduin.eldar.org \
    --to=brad@anduin.eldar.org \
    --cc=segaloco@protonmail.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).