What does HackerNews think of unix-history-repo?
Continuous Unix commit history from 1970 until today
This just ensures that the “why” is lost when someone comes looking years later.
From experience, SCM history is far more durable than just about any other work product we produce.
Over five decades later, commit history was still available for the Unix sources and could be reconstructed: https://github.com/dspinellis/unix-history-repo
I’ve used 35-year-old commit messages to help understand a long-standing issue, decades after all other related organization tooling and data had disappeared.
The Unix source - https://github.com/dspinellis/unix-history-repo - with quite a number of releases dating back to 1970.
http://www.nesssoftware.com/home/mwc/source.php
(Considered buying Coherent way back in the day)
There is an empty repo by this name in your project so I'm a bit confused whether this one is supposed to be included:
https://github.com/dspinellis/unix-history-repo
(previous discussion:) https://news.ycombinator.com/item?id=10995483
[1] https://github.com/dspinellis/unix-history-repo/tree/Bell-Re...
[2] https://github.com/dspinellis/unix-history-repo/tree/BSD-2-S...
https://github.com/dspinellis/unix-history-make (a repo with the scripts to build the final repo)
https://github.com/dspinellis/unix-history-repo (the final repo -- check out all of the different branches/tags)
In an interview I read, Tarn said something to the effect of that "he was not interested in learning about version control and it would just be a distraction that would take away time from the important work, since the way he works has worked for him for many years".
I can't help but think that first, it's a bit dangerous way to work, all "past, current and future" state of the project is only in his head and if he happens to become indisposed, the project is very very likely to die (though I suppose there would be hardcore fans willing to reverse engineer it)...
Second, it's a loss of historical record... imagine in fifty years historians wanting to analyze the project's history, it would be so much more useful to have a granular history instead of just a blob of files scattered across thousands of directories...
Just look at Unix History repository here for example: https://github.com/dspinellis/unix-history-repo - I think there's immense long term value in preserving this kind of archival history.
https://github.com/dspinellis/unix-history-repo.git
has different branches for various unix versions
Seems the earliest reference I could find in there was dated november 1973, but it is from a full import in 77:
commit c849507974bd2c0e2fd8c17e06f6f65b68075ca9 Author: Bill Joy Date: Wed Nov 23 12:43:50 1977 -0800
Start development on BSD 1
Create reference copy of all prior development files
Synthesized-from: 1bsd
Some of the earlier copies i can see were even just shell scripts: trap "" 1 15
if test -t 2>&1 ; then
echo "Sending output to 'nohup.out'"
exec nice -5 $* >>nohup.out 2>&1
else
exec nice -5 $* 2>&1
fi
Research-V3-Snapshot-Development did not have nohup
Research-V4-Snapshot-Development had the nohup man page but not nohup
Research-V5-Snapshot-Development has nohup.ccommit 0281f55d1cf7aa94555d8522d8b37161b97791be Author: Ken Thompson Date: Tue Nov 26 18:13:21 1974 -0500
Research V5 development
Work on file usr/source/s2/nohup.c
Co-Authored-By: Dennis Ritchie
Synthesized-from: v5
Then later v7 reverted back to the shell versioncommit 6144d5b3a973b515977eef01a828cdd82c480fe3 Author: Ken Thompson Date: Wed Jan 10 15:25:04 1979 -0500
Research V7 development
Work on file bin/nohup
Co-Authored-By: Dennis Ritchie
Synthesized-from: v7
The earlier i can find there without digging deep is BSD 4.4 Lite, a mega-commit by Rodney Grimes (https://github.com/dspinellis/unix-history-repo/commit/d2273...)
Being an enormous commit, changes are that it merged in existing stuff.