Mercurial vs. SVN vs. CVS vs. whatever
Posted: Fri Mar 23, 2012 7:48 am
I note that Jonsey posted a message on Caltrops (in the thread on the sudden increase in hard drive prices) how the Mercurial source code management system had a number of problems. If you've used other (non-proprietary) source code management systems like SVN or CVS, have you noticed a differerence? Or what do you think of the one you're using?
I've probably installed or used all three, as different projects have used different systems and if you want to organize the files used by them, or in some cases the only way to get their files, is to use their source code management system to retrieve them. And if you want to participate in submitting changes then you have to use the system.
I'm thinking of choosing one for a project I'm doing, and I'd like to find one that has a low to nonexistent probability of losing code in the repository, and has a standard system-integratable tool for checkout/commit. By "system-integratable" I mean it creates a set of commands attached to the standard explorer pop-up menu allowing for a file that is selected to be checked back in or checked out, and so on.
Tortoise releases a client for all three for Windows, and that's what I've used. Uh, it's three different clients, one for each repository type, not a single client that handles all three.
If you've used a proprietary source code librarying system, how does it compare? Some examples include
* Microsoft's Visual Source Safe, which was integrated into the software tools they sold back then (Visual Basic, Visual C), and apparently had problems with corrupting repositories
* Panvalet, a source code management system for mainframes.
I've probably installed or used all three, as different projects have used different systems and if you want to organize the files used by them, or in some cases the only way to get their files, is to use their source code management system to retrieve them. And if you want to participate in submitting changes then you have to use the system.
I'm thinking of choosing one for a project I'm doing, and I'd like to find one that has a low to nonexistent probability of losing code in the repository, and has a standard system-integratable tool for checkout/commit. By "system-integratable" I mean it creates a set of commands attached to the standard explorer pop-up menu allowing for a file that is selected to be checked back in or checked out, and so on.
Tortoise releases a client for all three for Windows, and that's what I've used. Uh, it's three different clients, one for each repository type, not a single client that handles all three.
If you've used a proprietary source code librarying system, how does it compare? Some examples include
* Microsoft's Visual Source Safe, which was integrated into the software tools they sold back then (Visual Basic, Visual C), and apparently had problems with corrupting repositories
* Panvalet, a source code management system for mainframes.