4 ms·
"Most of these problems simply didn't exist or were not nearly as severe with previous revision control systems" Are you kidding? :) CVS, Subversion, Perforce
by dpc_pw 10y ago
"Most of these problems simply didn't exist or were not nearly as severe with previous revision control systems"
Are you kidding? :)
CVS, Subversion, Perforce, and some propriety revisioning systems were HUGE PITA. People used to lock files, so noone else could change them when they were working with them. Merging different feature branches was like locking whole repository with huge lock, so noone else could touch anything at the time.
Any time I had to work with legacy revisioning systems I wanted to kill myself. Git workflows are conventions to help improve small issues with staff that wasn't even possible befor (before Distributed VCS). And a lot of these problems are superficial ("oh those merge commit are annoying in `git log`").
It reminds me: https://www.youtube.com/watch?v=ZFsOUbZ0Lr0 https://www.youtube.com/watch?v=ZFsOUbZ0Lr0
- jimbobimbo 10y agoIn Subversion you'd need to explicitly lock the file, it doesn't require it. Merge the is also not as bad as you're describing. I actually had more headaches with merges in Git than in Subversion.