>Fundamentally, I see corporate objections to git entirely as a lack of established workflows and repo server management tools I don't even understand that arg

>Fundamentally, I see corporate objections to git entirely as a lack of established workflows and repo server management tools I don't even understand that argument. To me, git feels EXTREMELY enterprisey. You can't USE the tool without defining a workflow, even on a simple project. That to me screams "bureaucratic control wet dream". Git lacks in the tools department on windows, and in the ability to make "workflow specific gui's" to operate on it. Fix that, and Git wins for 90% of cases vs SVN. Git is scary at first, but after you use it in the correct configuration for your task, you're like "oh, another tool, one that works pretty well" and you move on. I still feel dude hasn't seen the correct configuration for his task and want to point him at the configuration design bubbles in progit.