[MattBearman]

I've only just made the switch. Like most people I was stuck with SVN due to my employer using it, and refusing to update.

Now I'm freelance I've had the time to put into learning Git and I'm glad I did, but the point is there are still a lot of people using SVN, some of whom will switch to Git in the future, and posts like this can be very useful to them.

[icefox]

> and refusing to update.

How true this is. I spoke with one sysadmin who told me that even if 100% of the developers were using git-svn he would never allow git as the official location to store code on the servers and it must be pushed back to svn. I am not sure how to respond to people like that.

Edit: When pressed for more details it was clear that he was happy with his svn server setup and didn't want to change and have to learn something new. This was not a logical discussion, but an emotional one and as he ran the servers he had the final say.

[nicknyc]

"didn't want to change and have to learn something new"

Resistance to change might be an authority thing - you could just walk around this troll's bridge and see what happens. Try talking to his boss or higher about source control, casually. If his manager asked him to change to GIT he would do it. He might have dismissed you because he believes you're not in a position of power over him or the work required to switch is mundane.

[efsavage]

Good admins resist change. Great admins can tell you why.

[gaius]

It's possible that he was operating under constraints of which you were unaware. One thing that springs to mind is escrow.