Size: 723
Comment: new comparison chart. Please help!
|
Size: 2162
Comment: Explanations, note on hg rename.
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
||RCS Name ||Bazaar-NG||Arch||CVS||Subversion||Git||Hg || Monotone|| ||Decentralized || Yes || No || No||Yes ||Yes||Yes|| Yes || ||Simple/No Namespace||Yes ||Yes || No||No || ||No || No || ||Supports Renames|| Yes ||Yes || No||Yes || ||No?|| || ||Has Checkouts || Yes || No ||Yes||Yes || || || || ||Has Snapshots || Yes ||Yes ||Yes||Yes || || || || ||Supports Merge || Yes ||Yes || No||No ||No?|| ||Yes || ||Cherrypicks || Yes ||Yes ||Yes||Yes || ||Yes|| || ||Simple UI || Yes ||No ||No ||No ||No ||Yes||No || |
= Overview = ||RCS Name ||Bazaar-NG||Arch||CVS||Subversion||Git||Hg || Monotone|| Darcs || ||Decentralized || Yes ||Yes || No||No ||Yes||Yes || Yes ||Yes || ||Simple/No Namespace||Yes ||No || No||Yes || ||No ||No ||Yes || ||Optional Repository|| None||Req ||Req||Req || || || || || ||Supports Renames|| Yes ||Yes || No||Yes || ||No[#1 (1)]||Yes ||Yes || ||Has Checkouts || Yes ||Yes ||Yes||Yes || || || ||No || ||Has Revisions || Yes ||Yes ||No ||Yes || || || || || ||Smart Merge || Yes ||Yes|| No ||No ||No?|| ||Yes ||Yes || ||Cherrypicks || Yes ||Yes ||Yes||Yes || ||Yes || ||Yes || ||Plugins || Yes ||No ||No || || || || || || (note: it would be interesting to have a small benchmark too, like "time to run XXX diff/import/commit in the linux kernel",) = Details about each feature = == Decentralized == Whether the tool is designed to allow branches of the same project to be in different remote repositories. == Simple/No Namespace == The namespace is the way a revision control system identifies a revision uniquely. It can be user-visible (GNU Arch), or tool internal (bzr, git, ...). == Optional Repository == ? == Supports Renames == Whether the tool supports file renaming and merging changes to a renamed file. == Has Checkouts == A [Checkout checkout] is a working tree with a relatively small amount of metadata. == Has Revisions == ? == Smart Merge == Whether the tool is able to know which revisions have to be merged (recording merge history is a necessary condition for this). == Cherrypicks == Whether the tool records Cherrypick history. == Plugins == Whether the tool is extensible with plugins. = Footnotes = [#11 (11)] Support for renames in hg is being implemented. Unlike bzr, it uses rename history instead of unique file ID. |
This chart is a rough draft
Overview
RCS Name |
Bazaar-NG |
Arch |
CVS |
Subversion |
Git |
Hg |
Monotone |
Darcs |
Decentralized |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
Yes |
Simple/No Namespace |
Yes |
No |
No |
Yes |
|
No |
No |
Yes |
Optional Repository |
None |
Req |
Req |
Req |
|
|
|
|
Supports Renames |
Yes |
Yes |
No |
Yes |
|
No[#1 (1)] |
Yes |
Yes |
Has Checkouts |
Yes |
Yes |
Yes |
Yes |
|
|
|
No |
Has Revisions |
Yes |
Yes |
No |
Yes |
|
|
|
|
Smart Merge |
Yes |
Yes |
No |
No |
No? |
|
Yes |
Yes |
Cherrypicks |
Yes |
Yes |
Yes |
Yes |
|
Yes |
|
Yes |
Plugins |
Yes |
No |
No |
|
|
|
|
|
(note: it would be interesting to have a small benchmark too, like "time to run XXX diff/import/commit in the linux kernel",)
Details about each feature
Decentralized
Whether the tool is designed to allow branches of the same project to be in different remote repositories.
Simple/No Namespace
The namespace is the way a revision control system identifies a revision uniquely. It can be user-visible (GNU Arch), or tool internal (bzr, git, ...).
Optional Repository
?
Supports Renames
Whether the tool supports file renaming and merging changes to a renamed file.
Has Checkouts
A [Checkout checkout] is a working tree with a relatively small amount of metadata.
Has Revisions
?
Smart Merge
Whether the tool is able to know which revisions have to be merged (recording merge history is a necessary condition for this).
Cherrypicks
Whether the tool records Cherrypick history.
Plugins
Whether the tool is extensible with plugins.
Footnotes
[#11 (11)] Support for renames in hg is being implemented. Unlike bzr, it uses rename history instead of unique file ID.