News for hackers. Stuff that matters.
Re:History of version control - 10 astonishments by rythie on Saturday December 17, 2011 @09:45AM (#3364295)
It misses out BitKeeper, which inspired both Git and Mercurial, which was launched 5 years earlier.
Re:History of version control - 10 astonishments by rst on Saturday December 17, 2011 @10:30AM (#3364376)
It gives very short shrift to commercial source control systems generally. Two (VSS, and SCCS --- the latter part of the original AT&T Unix distributions, on the same closed-source terms) get mentioned in passing, but neither gets treated as a milestone.

That would include BitKeeper --- copies were available for a few years at no cost to Linux kernel developers, but only on increasingly restrictive terms, which McVoy ultimately wound up revoking altogether. IIRC, Linus released the first embryonic version of git within weeks after McVoy withdrew the free-as-in-beer version of BitKeeper.

Re:History of version control - 10 astonishments by nupark2 on Saturday December 17, 2011 @11:18AM (#3364464)
In terms of historical interest, it's also worth noting why McVoy restricted and eventually withdrew the BitKeeper license: Andrew Tridgell (of Samba and rsync) had begun reverse-engineering the protocol with the eventual intent of implementing a free client.

The resulting debacle was fairly ridiculous; Linux chastising Andrew Tridgell, continued flamewars about using a closed-source product.

What I find interesting here, though, is just how much hot water McVoy landed in. He gave away free licenses to Linux developers, then when someone in that community started reverse engineering his product with the intent to replace it, he revoked the free license, leading Linus to develop a replacement anyway -- one that has largely consumed the vast majority of BitKeeper's target market.

Re:History of version control - 10 astonishments by rst on Saturday December 17, 2011 @12:11PM (#3364574)
Tridge's reverse engineering was why McVoy withdrew the license, but he'd started to restrict it well before that. Initial releases were source-available, and had a "fail-safe" that would turn the code fully open source if McVoy's company ceased to function. Source access and the failsafe were withdrawn over time, and various restrictive clauses were added. (Most notably, around 2002, McVoy added a "non-compete" clause which purposted to restrict any user for gratis BK from working on a competing SCM for a full year after they last touched BK. I'm not sure that was ever tested in court.) Here's a brief description of the history:

http://better-scm.shlomifish.org/comparison/bk-license.html

Re:History of version control - 10 astonishments by JoshTriplett on Sunday December 18, 2011 @05:18AM (#3366372)
Andrew Tridgell recreated the "reverse engineering" you mentioned in front of a live audience at linux.conf.au not long afterward; see https://lwn.net/Articles/132938/ . Summary: he saw a port number in the standard bitkeeper URLs, tried telnetting to it, tried typing "help" which listed the available commands, and tried typing the "clone" command which spit SCCS files back at him. He walked through the process and literally had the audience shouting the appropriate commands at him the whole way through, demonstrating the obviousness of the process.
Re:History of version control - 10 astonishments by tomjen3 on Saturday December 17, 2011 @04:16PM (#3365140)
Well if I recall correctly his reverse "engineering" consisted of figuring out that the protocol was a plain-text English based protocol (i.e it would be like if you were to reverse engineer FTP by looking at the TCP stream).
Re:History of version control - 10 astonishments by ghshephard on Saturday December 17, 2011 @11:43AM (#3364512)
Misses the absolutely massive Clearcase. In 1999, (and earlier, but I ran into in 1999 at Loudcloud) - if you wanted to support multiple branches and allow merging code into them, it was the only tool that made it easy. Had great (windows) client side environment that gave everyone a "view" into the source, But _man_ was the backend ugly.
Re:History of version control - 10 astonishments by undees on Saturday December 17, 2011 @05:50PM (#3365315)
ClearCase is certainly popular, but I don't think it ever had a feature that was a big milestone in version control history. Client side software with a view of the source is already covered in the author's point #4, and ClearCase doesn't do this better than the others (quite the contrary, in my experience).
Re:History of version control - 10 astonishments by ghshephard on Monday December 19, 2011 @04:19AM (#3369060)
Clearcase had two new additions: Branching/merging made easy(ier?) and the source code under version control was seen as a file system, a drive letter on your windows system.
Re:History of version control - 10 astonishments by tedunangst on Saturday December 17, 2011 @11:49AM (#3364533)
I'd agree with that, but the article seems focused on a linear progression, where clearcase is more of a fork that nobody else followed.
Re:History of version control - 10 astonishments by sklnd on Saturday December 17, 2011 @11:46AM (#3364524)
It also completely ignores earlier distributed source control projects like GNU Arch. 2005 was when there was an open source distributed VCS that was fast and pleasant to use, but implementations of the idea are older than that.
Re:History of version control - 10 astonishments by qjz on Saturday December 17, 2011 @03:45PM (#3365073)
Darcs merits a nod, as well.
Re:History of version control - 10 astonishments by Create on Saturday December 17, 2011 @11:08AM (#3364447)
Misses also GOOG's dearly Perforce.
Re:History of version control - 10 astonishments by InclinedPlane on Saturday December 17, 2011 @05:05PM (#3365237)
This article isn't meant to be a comprehensive list of all SCM systems or even all of the important ones. It's just a list of all of the big technological advancements. Perforce is a good system but it was never revolutionary.
Re:History of version control - 10 astonishments by tedunangst on Saturday December 17, 2011 @11:46AM (#3364523)
There is nothing particularly astonishing about perforce. What makes you think it should have been included?
Re:History of version control - 10 astonishments by to3m on Saturday December 17, 2011 @06:18PM (#3365364)
If you ignore all the distributed "stuff", and the workflow enhancements it permits, and assume everybody is always connected to the server and attached via a LAN, you can just concentrate on doing a reasonably good job of handling very large quantities of data, including very large binary files. (Apologies for not trying to reproduce the breathless style of headline.) As is common, the article presupposes that decentralization is unambiguously progress, but that isn't true in all respects.

People often complain about the idea of using version control for large binary files, as if it is unreasonable to want such a thing, and that as a point of principle version control systems should contain only text files, and the fact that many version control systems support this poorly is proof that you don't want it anyway. But there are actually people who create, with their own hands, large binary files, often of the completely-unmergeable variety, and they deserve version control just as much as the programmers do.

(And then once you have a system that works well for them, you can then use it to solve all manner of problems that might previously have involved storing files in public folders, mailing them round, or maybe just waiting for them to compile again. No need for any of that crap any more - just check the files in, they're there forever, and you can get them back quickly.)

Re:History of version control - 10 astonishments by rue on Sunday December 18, 2011 @12:47AM (#3366051)
> As is common, the article presupposes that decentralization is unambiguously progress, but that isn't true in all respects.

It is, in the sense that a decentralized VCS is, essentially, a superset of a centralized one.

…

Blobs are certainly still an issue, though orthogonal to distribution (I don't think you intended to imply it was related, but it could be read as if you did).

Re:History of version control - 10 astonishments by to3m on Sunday December 18, 2011 @12:33PM (#3367011)
Well, I don't mean to imply that binary files are inherently impossible to handle using a decentralized system. In fact, I have some PDFs and PNGs in my git repository, and git has managed not to make a mess of them. But I still think binary files are difficult for distributed systems to support well.

Distributed systems rely on allowing people to (in effect) create multiple versions of the same file, and then merge them all together later. But it's very rare that binary files are mergeable! And if the file can't be merged, the distributed approach won't work. People will step on one another's changes by accident, and people will have to redo work.

The usual solution is simply not to allow multiple versions to exist: enforce some kind of locking system, so that each editor has to commit their changes before the next one can have a go. But now you need some centralized place to store the locking information...

Re:History of version control - 10 astonishments by tedunangst on Saturday December 17, 2011 @09:23PM (#3365702)
I never had a problem using cvs for what I considered large binaries. Certainly we kept using cvs long after mostly switching to bk because cvs worked better for binaries. Perforce never seemed like a big deal, just cvs with a little more.
Re:History of version control - 10 astonishments by nitrogen on Sunday December 18, 2011 @02:03AM (#3366161)
Due to CVS's (or RCS's?) text-based file format and conversion of line endings when checking out a repository, migrating binary files across operating systems can cause mangling of bytes whose value equals that of CR and LF.
Re:History of version control - 10 astonishments by cpeterso on Saturday December 17, 2011 @02:29PM (#3364908)
Google's Perforce?
Re:History of version control - 10 astonishments by TomasSedovic on Saturday December 17, 2011 @05:05PM (#3365236)
I read the "GOOG's dearly" part as "dear to Google" not "developed by Google". Google did use Perforce in the past and they still do, probably.

I think that the GP used the phrase correctly, but not being a native English speaker myself, I'm not entirely sure.

Re:History of version control - 10 astonishments by paulhauggis on Saturday December 17, 2011 @01:09PM (#3364702)
I believe perforce handles large binaries as well.
Re:History of version control - 10 astonishments by tonfa on Saturday December 17, 2011 @10:03AM (#3364320)
Monotone gave most inspiration according to the authors of git and hg.

But the author addresses the point anyway: > I’m not recording the first time anyone made the astonishing thing, but the first time it was productised and became popular.

Re:History of version control - 10 astonishments by ajross on Saturday December 17, 2011 @10:26AM (#3364364)
Torvalds was expressly trying to replace bitkeeper when he wrote git. And I'm not sure anything he said about other systems might be considered "inspiration".

But that said, git really isn't very similar to bitkeeper except insofar as it enables distributed development. Both model development as a forest of independent developer trees which communicate with each other through merges. But bitkeeper is still a traditional centralized server keeping a bunch of delta'd files.

Re:History of version control - 10 astonishments by andrewflnr on Saturday December 17, 2011 @01:09PM (#3364701)
According to Wikipedia[1], he liked some of its features, and seemed to float it as a model for a replacement.

[1] http://en.wikipedia.org/wiki/Monotone_(software)#Monotone_as...

Re:History of version control - 10 astonishments by tedunangst on Saturday December 17, 2011 @11:42AM (#3364511)
bitkeeper only has a central server to the same extent that git does. Somebody on the team picks a repo and says "this one is for serious" and that's it.

The decision bitkeeper made to keep files in SCCS format was of course not revolutionary, but tells you quite a bit about the target market (people who had makefiles that relied on implicit commands like get just working). They went to extra effort to make it look just a bunch of delta'd files.

Re:History of version control - 10 astonishments by piotrSikora on Sunday December 18, 2011 @08:49AM (#3366609)
It also misses NSElite (later Teamware), which, in Larry McVoy's words, was BitKeeper's grandparent.