The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dds@aueb.gr (Diomidis Spinellis)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Wed, 30 Mar 2016 10:53:58 +0300	[thread overview]
Message-ID: <56FB8616.6060908@aueb.gr> (raw)

The Unix History repository on GitHub [1] aims to provide the evolution 
of Unix from the 1970s until today under Git revision control.  Through 
a few changes recently made [2] it's now possible for individual 
contributors to have their GitHub profile linked to their early Unix 
contributions.  Ken Thompson graciously made this move last week 
following a personal email invitation.  I think it would be really cool 
if more followed.  This would send a powerful message of continuity and 
tradition in computing to youngsters joining GitHub today.

What you need to do is the following.

- Create a GitHub profile (if you haven't already got one)
- Click on https://github.com/settings/emails
- Add the email address(es) associated with your early Unix commits 
(e.g. foo at research.uucp or bar at ucbvax.berkeley.edu). You can easily find 
an author's commits and email addresses recorded in the repository 
through the web search form http://www.spinellis.gr/cgi-bin/namegrep.pl
- GitHub will tell you that a verification email has been sent to your 
(probably defunct) email address.  Don't worry.  Your account will be 
linked to the address even without the verification step.
- Adding your photograph to your profile will increase the vividness of 
GitHub's revision listings.

If you're in contact with Unix contributors who are not on this list, 
please forward them this message.  Also, if your name isn't properly 
associated with the repository's commits, drop me an email message (or a 
GitHub pull request for the corresponding file [3]), and I'll add it.

[1] https://github.com/dspinellis/unix-history-repo
[2] The modifications involved the change of UUCP addresses to use the 
.uucp pseudo-domain rather than a ! path and the listing of co-authors 
within the commit message.
[3] 
https://github.com/dspinellis/unix-history-make/tree/master/src/author-path

Diomidis - http://www.spinellis.gr


             reply	other threads:[~2016-03-30  7:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  7:53 Diomidis Spinellis [this message]
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
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=56FB8616.6060908@aueb.gr \
    --to=dds@aueb.gr \
    /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).