Comparison between Superversion

Back to main page

SCM feature:	Superversion	Add to comparison: +CVS +AccuRev +Aegis +AllChange +Arch +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +Co-Op +Darcs +Git +LibreSource Synchronizer +Mercurial +Monotone +OpenCM +Perforce +PureCM +SourceAnywhere +Subversion +Surround SCM +svk +Team Foundation Server +Vesta +Visual SourceSafe
Atomic Commits	Commits are atomic.
Files and Directories Moves or Renames	No. Renames are not supported.
Intelligent Merging after Moves or Renames	No. Renames are not supported.
File and Directories Copies	No. Copies are not supported.
Remote Repository Replication	Yes.
Propagating Changes to Parent Repositories	No.
Repository Permissions	No.
Changesets' Support	Partial support. Changes are grouped into changesets, but cannot be cancelled invididually yet.
Tracking Line-wise File History	No.
Ability to Work only on One Directory of the Repository	No.
Tracking Uncommited Changes	Yes. Local changes are detected and shown immediately. Changes can be collected in a local buffer before being committed to the repository.
Per-File Commit Messages	Yes.
Documentation	Fairly poor. There are two tutorials, but there is no reference. Installing and getting started with the GUI is very easy though.
Ease of Deployment	If Java 1.4 is installed, deployment of Superversion usually takes two clicks.
Command Set	There is little need to memorize a command set because all actions take place in a GUI. A part of the terminology used in the application is borrowed from CVS.
Networking Support	Good. Network support based on RMI is integrated seamlessly. Encryption and HTTP tunnelling are planned for the near future.
Portability	Excellent. Clients and servers work on any Java 1.4-compatible platform. There is official support for Windows, Linux and OS/2.
Web Interface	No.
Availability of Graphical User-Interfaces.	A GUI is integrated.