Comparison between Monotone

Back to main page

SCM feature:	Monotone	Add to comparison: +CVS +AccuRev +Aegis +AllChange +Arch +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +Co-Op +Darcs +Git +LibreSource Synchronizer +Mercurial +OpenCM +Perforce +PureCM +SourceAnywhere +Subversion +Superversion +Surround SCM +svk +Team Foundation Server +Vesta +Visual SourceSafe
Atomic Commits	Yes.
Files and Directories Moves or Renames	Yes. Renames are supported.
Intelligent Merging after Moves or Renames	Unknown. FILL IN.
File and Directories Copies	Yes. Copies are supported
Remote Repository Replication	Yes.
Propagating Changes to Parent Repositories	Yes.
Repository Permissions	Yes. It is possible to restrict incoming changes from certain sources to be performed only in certain parts of the repository.
Changesets' Support	Yes. Changesets are supported.
Tracking Line-wise File History	Yes, as of version 0.19.
Ability to Work only on One Directory of the Repository	It is possible to commit changes only in a subset of the tree. However, one must extract the entire tree to work on it.
Tracking Uncommited Changes	Yes. In a similar fashion to CVS.
Per-File Commit Messages	Yes. It is possible to attach a comment to a certain file at a certain revision.
Documentation	Good. There's an overview and tutorial written in Texi, and a man page. The client supplies documentation for every command.
Ease of Deployment	Excellent. It is possible to copy or compile the executable to the user's machine, without any configuration or external dependencies.
Command Set	Tries to follow CVS conventions, but deviates where there is a different design.
Networking Support	Good. Uses a custom protocol called "netsync".
Portability	Excellent. Executable is portable across all UNIXes and Win32.
Web Interface	No.
Availability of Graphical User-Interfaces.	No GUIs are available.