A Guide to Distributed Version Control Systems
July 6, 2008 – 11:16 amThis guide at InfoQ is a nice counterpoint to my list of reasons for not switching to Git.
Data is zeroes and ones — software is zeroes and ones and hard work.
This guide at InfoQ is a nice counterpoint to my list of reasons for not switching to Git.
2 Responses to “A Guide to Distributed Version Control Systems”
It’s interesting that ~1/3 of those polled used DVCSes for working with 0-1 other people.
My number one reason for using DVCSes is that they’re simpler to start. Since you don’t have to point everything at a central repository, it’s really trivial to version a directory.
mkdir newproject
cd newproject
vim __init__.py
bzr init .
bzr add .
bzr commit . -m “Rough Draft.”
My second reason? Local commits. I’ve got code checked out on my server, workstation, and laptop. I use a centralized workflow to keep them all in sync, but if I’m away from network connectivity I can still hack on what I’ve got on my laptop and commit each bugfix/feature as I complete it. Why should those features go away when the network does?
By Cody C. on Jul 6, 2008
Since that article was posted, Bazaar was adopted by MySQL: http://blogs.mysql.com/kaj/2008/06/19/version-control-thanks-bitkeeper-welcome-bazaar/
By Dmitri on Jul 8, 2008