From collabNet_Inc@mail.vresp.com (vresp is a bulk mailer):
Are you stuck with your companyââ¬â¢s outdated source control management system? Does your system get in the way of working productively? Are you constantly looking for ways to work around the tool because it doesnââ¬â¢t understand how developers work? Is the cost and pain of maintaining your SCM system getting out of control?
I answered "Yes" to every one of those questions. So, I'm stuck with what I have, it gets in the way, and I have to program around it. I wish I could dump it, but I need something the everyone can use. What should I do? Calgon, take me away!
Itââ¬â¢s time to move to Subversion.
Oh, wait, that's what I have now, and it's getting in my way and I have to find ways to work around it. We've been moving all of our stuff at Stonehenge to git, but Google Code and Sourceforge still use Subversion.
I'm thinking about using git for my next module just to see how it goes. It will probably be the same as the other modules: people won't use the repository and will just send patches.
Obviously, they're suggesting you put the svn repository itself under version control!
Remember, every problem can be solved with another layer of indirection, except too many layers of indirection...
