News for hackers. Stuff that matters.
Re:Show HN: BitKeeper – Enterprise-ready version control, no... by pklausler on Tuesday May 10, 2016 @01:29PM (#11668929)
In short, RCS maintains a clean copy of the head revision, and a set of reverse patches to be applied to recreate older revisions. SCCS maintains a sequence of blocks of lines that were added or deleted at the same time, and any revision can be extracted in the same amount of time by scanning the blocks and retaining those that are pertinent.

Really old school revision control systems, like CDC's MODIFY and Cray's clone UPDATE, were kind of like SCCS. Each line (actually card image!) was tagged with the ids of the mods that created and (if no longer active) deleted it.

Re:Show HN: BitKeeper – Enterprise-ready version control, no... by rbsmith on Tuesday May 10, 2016 @09:43PM (#11672078)
| CDC's MODIFY and Cray's clone UPDATE, were kind of like SCCS

Do you have references? I've heard of these but haven't come across details after much creative searching since they are common words.

Re:Show HN: BitKeeper – Enterprise-ready version control, no... by pmcjones on Tuesday May 10, 2016 @10:38PM (#11672281)
Re:Show HN: BitKeeper – Enterprise-ready version control, no... by rbsmith on Tuesday May 10, 2016 @10:52PM (#11672352)
Thank you! A peek into the (as far as I know) into root node of source control history.
Re:Show HN: BitKeeper – Enterprise-ready version control, no... by luckydude on Tuesday May 10, 2016 @09:55PM (#11672128)
I've heard that too. It comes from card readers somehow.