A large part of the Open Source world seems hot on git these days (and DVCSs in general). I can kinda see why. For tracking changes, the notion of a commit definitely makes more sense than updating the versions on files that CVS has to offer. The ease of creating git repos plays well with one of my own beliefs, which is "Even for one's own little projects, if it's not in a VCS it may as well be written on the back of a napkin". Social coding sites like
GitHub offer an ease of contributing to projects that contributors love, and git makes it easier to keep contributions (commits) from going stale than when dealing with patches in email or bug tacking systems. Git itself has useful tools for visualizing your repo (like
gitk), tracking down when a bad behaviour was introduced (
git blame), and a dozen others besides.
And for those that miss their
C roots, you can pretend your git hashes are pointers:
5eec2b04a70f704a7cdc1b77db59bb90ec03dd68 :-)
With the Eclipse Foundation also interested in supporting git as its main VCS, the
Eclipse Project decided to move to git at the beginning of the Juno Release cycle. I've been involved with the Platform UI component migration.
I'll write a second post soon with more details about the problems we encountered and some of the steps we took, but after a grueling 2 weeks the conversion of this component is done. Woo Woo!
- git://git.eclipse.org/gitroot/platform/eclipse.platform.runtime.git
- git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git
- git://git.eclipse.org/gitroot/e4/org.eclipse.e4.tools.git
