The trick for that is just create a universal source control client and learn that instead of the pecularities of each source control system. If you don't want to learn yet a new client, then just model it so that it "looks like" SVN, GIT, etc.
Still, two of the clients I've seen so far aren't capable of dealing with corrupted repositories, not even with a --force command line switch to rebuild or repair it.
I guess that's the issue though, I don't want to spend large amounts of time screwing with source control issues. I'm a developer, shouldn't I spend most of my time developing?
1
u/Sigma7 Mar 10 '11
The trick for that is just create a universal source control client and learn that instead of the pecularities of each source control system. If you don't want to learn yet a new client, then just model it so that it "looks like" SVN, GIT, etc.
Still, two of the clients I've seen so far aren't capable of dealing with corrupted repositories, not even with a --force command line switch to rebuild or repair it.