From: rochkind@basepath.com (Marc Rochkind)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Wed, 30 Mar 2016 10:30:03 -0600 [thread overview]
Message-ID: <CAOkr1zWoZGuLSKFtKA55oq2qendTEgx_j5v26Psqe9M6MmfYpg@mail.gmail.com> (raw)
In-Reply-To: <56FBF576.2000103@aueb.gr>
BSD is the new kind on the block. I don't think it came along until 1977 or
so. Research UNIX I don't think picked up SCCS ever. SCCS first appeared in
the PWB releases, if you don't count the earlier version in SNOBOL4 for the
IBM mainframes.
--Marc
On Wed, Mar 30, 2016 at 9:49 AM, Diomidis Spinellis <dds at aueb.gr> wrote:
> On 30/03/2016 17:25, Marc Rochkind wrote:
>
>> What do you mean by "early"? All of my early work was done under my
>> login "marc", and in those days to email we just typed:
>>
>> % mail marc
>>
>> Email was internal to the system. Email between machines came along later.
>>
>> Also, I don't think we ever used the word "commit." Actually, much of my
>> early work predated the introduction of SCCS. ;-)
>>
>
> I should have been more clear. The Unix history Git repository contains
> synthetic commits imported from snapshots, patches, SCCS, CVS, and Git
> files. I took the liberty of attaching the email ID at research.uucp on all
> Bell Labs commits, even though many predate UUCP email.
>
> Your SCCS work belongs to the mysterious subset of Bell Labs commands that
> made their first public appearance on BSD Unix. I didn't find SCCS included
> in the 6th or 7th Research Edition, nor in Unix 32/V, which, I understand,
> were the ancestors of BSD.
>
> Specifically, I first find SCCS included in the BSD-4 snapshot (e.g.
> usr.bin/sccs/sccs.c) and also in the BSD SCCS repositories predating BSD-4,
> through commits such as the following.
>
> commit 20f9634be56fa471a34bc386dcc4c04f9587791d
> Author: Eric Allman <eric at ucbvax.Berkeley.EDU>
> Date: Tue May 13 07:23:29 1980 -0800
>
> changed path to SCCS/s.
> added chghist & help
> generalized argument chomping
>
> SCCS-vsn: 1.2
>
>
> Other commands that fall into this category include fsck (frodo), gres
> (lem), efl (sif), diction (llc), and ideal (cvw). Somebody has commented on
> this list that a secret tunnel linked Murray Hill and Berkeley. I'd welcome
> any better explanations you may have.
>
>
> I'll find a way to graft you as the developer of SCCS somewhere between
> BSD3 and BSD4, so please do claim marc at research.uucp on GitHub. Are
> there other files I should also attribute to you?
>
>
> Diomidis
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160330/8a6c5175/attachment.html>
next prev parent reply other threads:[~2016-03-30 16:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 7:53 Diomidis Spinellis
2016-03-30 12:31 ` Joerg Schilling
2016-03-30 13:10 ` Diomidis Spinellis
2016-03-30 13:44 ` Joerg Schilling
2016-03-30 19:17 ` Larry McVoy
2016-03-30 21:07 ` Random832
2016-03-30 23:03 ` Joerg Schilling
2016-03-31 3:20 ` Larry McVoy
2016-03-31 3:34 ` Random832
2016-03-31 3:40 ` Larry McVoy
2016-03-30 23:42 ` Joerg Schilling
2016-03-31 3:54 ` Larry McVoy
2016-03-30 14:25 ` Marc Rochkind
2016-03-30 15:23 ` Joerg Schilling
2016-03-30 19:14 ` Larry McVoy
2016-03-30 15:49 ` Diomidis Spinellis
2016-03-30 16:07 ` Joerg Schilling
2016-03-30 16:29 ` Diomidis Spinellis
2016-03-30 16:14 ` Pat Barron
2016-03-31 21:06 ` Clem Cole
2016-03-31 21:54 ` Ron Natalie
2016-04-01 9:01 ` Diomidis Spinellis
2016-04-01 14:41 ` Clem Cole
2016-04-01 21:00 ` Jeremy C. Reed
2016-04-01 13:06 ` Dave Horsfall
2016-04-01 21:52 ` Pat Barron
2016-03-30 16:30 ` Marc Rochkind [this message]
2016-03-30 16:40 ` Joerg Schilling
2016-03-30 16:55 ` John Cowan
2016-03-30 18:28 Norman Wilson
2016-03-30 20:06 ` Ronald Natalie
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=CAOkr1zWoZGuLSKFtKA55oq2qendTEgx_j5v26Psqe9M6MmfYpg@mail.gmail.com \
--to=rochkind@basepath.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).