Don't be a git, use subversion
mkaz.com
mkaz.com
There is no reason that you can't use git as a master repository system--that's how most people treat GitHub anyway.
OTOH if you want to do anything besides the basic commit or update with Subversion, it's ridiculously difficult. Subversion is a SCM tool where people actually prefer to merge manually rather than deal with its conflict handler.
It will save you a command on every commit, no need to commit and then push.
Git use causes smaller incremental commits, which can be squashed into bigger ones for re-merging, but makes for better, more ambitious changes, and easier rollbacks to working code. You get 85% of the benefit by allowing those who can handle it to use git as a subversion client.
This article explains the complexity well: http://steveko.wordpress.com/2012/02/24/10-things-i-hate-abo...
Git is complex for you. The mistake you're making is in not realising that's not universally true.
I still see git requiring more commands for simple tasks and the model of what is happening has more moving parts (more complex). This gives git the ability to do a lot more, but my thought is for the majority you don't need the more.
My thought was just simplify and subversion might be the right tool for many jobs.
Everyone thinks I'm a fool.
As far as stats, if you really are curious. I received about 1,600 views on the article. Oddly no referrer data from HN, around 300 from Twitter, 150 from Google Reader and 100 from hckrnews.com.