Starting from today SZARP uses Git as a source version control. The reasons for change are likely similar as for other projects that move from centralized SCM systems like CVS/SVN to distributed and more feature-rich like Git/Baazar/Mercurial. Git was chosen for it’s stability, maturity, speed and extensive branching/merging capabilities.
Project still uses SourceForge, you can get source code using command like:
git clone git://szarp.git.sourceforge.net/gitroot/szarp/szarp
The side-effect of this transition can be a less frequent updating of Szarp version – previous scheme was using Subversion revision numbers as version numbers. Since Git does not use numeric revision identifiers, versions will be upgraded manually and will more closely reflect changes in functionality. | Starting from today SZARP uses Git as a source version control. The reasons for change are likely similar as for other projects that move from centralized SCM systems like CVS/SVN to distributed and more feature-rich like Git/Baazar/Mercurial. Git was chosen for it’s stability, maturity, speed and extensive branching/merging capabilities.
Project still uses SourceForge, you can get source code using command like:
git clone git://szarp.git.sourceforge.net/gitroot/szarp/szarp