From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Wed, 30 Mar 2016 18:07:51 +0200 [thread overview]
Message-ID: <56fbf9d7.1yqxiR22dfkSvoRR%schily@schily.net> (raw)
In-Reply-To: <56FBF576.2000103@aueb.gr>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
Diomidis Spinellis <dds at aueb.gr> wrote:
> 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
It seems that you confuse the program "sccs" from Eric Allman with SCCS in
general.
sccs see: http://sccs.sourceforge.net/man/sccs.1.html
is a wrapper program that helps to use the SCCS worker programs.
"sccs" was written at UC Berkeley since Max 10 1980.
Check the bottom SEE ALSO paragraph.
admin cdc comb delta get help prs prt rmdel sact unget val
are the worker programs that predate the existence of the "sccs"
program by many years.
These programs have been written at AT&T by Marc.
BTW: The SCCSv4 history format was introduced February 18, 1977 and is still
understood by recent software.
CSRG includes the UCB history for the AT&T SCCS commands as well, but they have
not been legally available before December 20 2006. The AT&T sources "slipped"
into the CSRG archives and nobody really complained ;-)
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/
next prev parent reply other threads:[~2016-03-30 16:07 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 [this message]
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
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=56fbf9d7.1yqxiR22dfkSvoRR%schily@schily.net \
--to=schily@schily.net \
/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).