From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Wed, 30 Mar 2016 17:23:00 +0200 [thread overview]
Message-ID: <56fbef54.lHKH01u78tt6Wr8X%schily@schily.net> (raw)
In-Reply-To: <CAOkr1zUow1CNrP_ZRMD1FxoAD2+kZkspEX3iLz-ZHGBeQBQTsQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
Marc Rochkind <rochkind at basepath.com> 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. ;-)
Good point!
Checking the sccs -R log output from the CSRG archives of course at the bottom
gives something like:
Wed Apr 9 16:02:50 1980 bill
* ./sys/kern/kern_resource.c 3.1
date and time created 80/04/09 16:02:50 by bill
Wed Apr 9 16:02:48 1980 bill
* ./sys/vax/vax/Locore.c 3.1
date and time created 80/04/09 16:02:48 by bill
Tue Dec 4 15:58:14 1979 bostic
* ./usr.bin/ctags/ctags.c 4.1
3bsd version
and we need to know that "bostic" is the login from Keith Bostic and "bill" is
the login from Bill Joy.
I am not sure whether there ever was something like user at domain in version
control before BitKeeper SCCS has been introduced.
BTW: the introduction of SCCS was early, at that time I had no access to more
than a desktop calculator.
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 15:23 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 [this message]
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
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=56fbef54.lHKH01u78tt6Wr8X%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).