I've done what I usually do and checked the blogs. Here is one article: http://tomayko.com/writings/the-thing-about-git which at the end refers to Workflow. I'd rate it alongside Tim's parable. Not that I understand all of it, especially the last bit.
Git is complex. There is no doubt about that. There are lots of ways do to things. The key it seems is to sort out a workflow to enable you to do what you want to do. I've read several articles now, and tend to give up 2/3 the way through. The model under the hood still disturbs my mind. One of my friends up north with potentially several insitutions to host for has bought in help to set up GIT. It seems to have been worth the money. You have simple and clean way to upgrade, and manage a few add-ons.
Am I correct here: getting to grips with GIT helps speedy upgrades, flexibility in what you do and how you do it? It actually becomes less of a "Big Deal" to upgrade. You can pull a small fix.
So remains the problems of plugins. Is this true: you can know which GIT brances contain the plugins and pull the most recent code as well, including small one line fixes? Putting this together, is this worth the effort? It seems to me that it is.
The GIT thoughts I've read often are quite poetic and philosophical (some programmers can write well), as well as quite blunt and opinionated. I was interested at how well Linus seemed to know the options out there.
And some random links:
- http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/ (186 comments)
- Think like a GIT: http://think-like-a-git.net/sections/git-makes-more-sense-when-you-understand-x.html
-Derek