Comparison between OpenCM

Back to main page

SCM feature:	OpenCM	Add to comparison: +CVS +AccuRev +Aegis +AllChange +Arch +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +Co-Op +Darcs +Git +LibreSource Synchronizer +Mercurial +Monotone +Perforce +PureCM +SourceAnywhere +Subversion +Superversion +Surround SCM +svk +Team Foundation Server +Vesta +Visual SourceSafe
Atomic Commits	Yes. Commits are atomic.
Files and Directories Moves or Renames	Yes. Renames are supported
Intelligent Merging after Moves or Renames	Unknown.
File and Directories Copies	No. Copies are not supported.
Remote Repository Replication	No.
Propagating Changes to Parent Repositories	No.
Repository Permissions	Permissions are defined on a per-branch basis.
Changesets' Support	Yes. Changesets are supported.
Tracking Line-wise File History	Unknown. Probably not.
Ability to Work only on One Directory of the Repository	No. All changes are made to a project as a unit
Tracking Uncommited Changes	Yes. Using cm diff
Per-File Commit Messages	Unknown.
Documentation	Well documented.
Ease of Deployment	Very good. Install the RPM, or build from tarball and install the init script.
Command Set	A CVS-like command set that is familiar to existing CVS users.
Networking Support	Good. Uses its own proprietary client/server protocol.
Portability	Good. Portable across all UNIX systems.
Web Interface	No.
Availability of Graphical User-Interfaces.	No GUIs are available.