Fair enough you don't like it, and you probably don't need it. But if the team decides to use a tool, it is still kind of stupid, and just a little stubbornly u

Fair enough you don't like it, and you probably don't need it. But if the team decides to use a tool, it is still kind of stupid, and just a little stubbornly unprofessional to cause them extra effort just to put up with your dislike of it - which is the case I'm describing. I mean I really dislike Visual studio and C#, but for reasons out of my control, we have to use it for a couple of projects. I could complain the whole time how it's not what I want, but instead I'm just doing it, because that's the job right now. I don't make the guy who doesn't like git (but is good at VS) come fix my environment or undo my mistakes every 3 days. My point was, the github svn support at least mitigates that scenario, whether or not it should happen.