Re:Why Google stores billions of lines of code in a single r...
by davidgay on Saturday December 09, 2017 @11:23PM
(#15889901)
No, before git the standard was svn, and before that, cvs. The switches happened even though there was an existing standard.
Re:Why Google stores billions of lines of code in a single r...
by progre on Sunday December 10, 2017 @04:31AM
(#15890663)
Having worked with all three, nothing but Stockholm syndrome would keep anyone to switch from cvs. Likevise the switch to git for open source happend (In my opinion) in large part because Github offers a far better experience than SourceForge witch was dominant at the time.
Re:Why Google stores billions of lines of code in a single r...
by boulos on Sunday December 10, 2017 @06:27AM
(#15890964)
There was actually a brief period where Google Code was ascendant, but then GitHub was demonstrably investing more in collaboration.
I think one aspect of Git that is really important is forking, and having your own local commits. Merging commits and patches in svn were awful. You wouldn't ever allow someone random to join your svn repo, but if they can reasonably provide a patch, you could take it. Git makes that massively easier.
A lot of companies don't use git.