From: brantley@coraid.com (Brantley Coile)
Subject: [TUHS] Caldera ancient UNIX license question
Date: Mon, 13 Aug 2012 06:52:34 -0500 [thread overview]
Message-ID: <0C96DD13-9C9C-4668-A488-023FC0C26689@coraid.com> (raw)
In-Reply-To: <201208130828.q7D8S0Va011757@freefriends.org>
maybe Norman could speak to the attitudes about source code control and the perceived need for it.
sent from my ipad
On Aug 13, 2012, at 2:32 AM, "arnold at skeeve.com" <arnold at skeeve.com> wrote:
> Larry McVoy <lm at bitmover.com> wrote:
>
>>> I'm
>>> sure there are other (mainly smaller) examples, though since we
>>> used no source-code control mechanism, tracing the details is
>>> non-trivial.
>>
>> No SCCS? When did Rochkind do SCCS? Wasn't it early 70's? I gotta believe
>> there is SCCS history out there. And for the record, BitKeeper can read it.
>
> I think Norman's point was that the Research guys didn't use a source
> code control system. SCCS was around and documented in System III in 1980,
> so it was probably done before then, but not in the research group.
>
> Arnold
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2012-08-13 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 2:59 Norman Wilson
2012-08-13 4:02 ` Larry McVoy
2012-08-13 8:28 ` arnold
2012-08-13 11:52 ` Brantley Coile [this message]
2012-08-13 13:05 ` Ronald Natalie
2012-08-13 14:24 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2012-08-10 19:30 סטֵפָן פָּבִיקֵבִיק
2012-08-10 20:47 ` ron
2012-08-10 21:42 ` Benjamin Huntsman
2012-08-11 7:51 ` Wesley Parish
2012-08-11 18:33 ` Tim Newsham
2012-08-11 19:08 ` Warner Losh
2012-08-11 23:04 ` A. P. Garcia
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=0C96DD13-9C9C-4668-A488-023FC0C26689@coraid.com \
--to=brantley@coraid.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).