No experience with git yet, but would be interested to see comments on this article...

Events happening in the community are now at Drupal community events on www.drupal.org.
maxxtraxx's picture

Comments

The problems described in

christefano's picture

The problems described in that blog post are present in all version control systems. An example is found in the author's follow up article, Still hatin’ on git: now with added Actual Reasons!, where he has a conflict because he didn't update his local copy before modifying part of it. Git is known for making branching and merging ridiculously easy (at least compared to other VCS's) and that's probably what the author should have done.

Git is powerful

Anonymous's picture

...and sometimes that power is a bit difficult to adjust to. But I take issue with the characterization that git "doesn't degrade gracefully". There is a small adjustment to one's workflow using git vs. CVS/svn, but it is a small price to pay for conveniences like 'git stash' and automatic branch/merge tracking. And gitk for visualizing how multi-committer code is evolving is fabulous!

I'll admit that all that power under the hood got me in trouble the first week or so I was using it - but the folks on the git irc channel are really helpful to get newbies out of a jam. Every time I have to go back to code I manage in CVS and svn, I curse.