|
Size: 4804
Comment: Why were all those informations deleted ???
|
Size: 4378
Comment: Brought footnotes back as a details section
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| ||RCS Name ||Bazaar-NG||Arch||CVS ||Subversion ||Git ||Hg ||Monotone||Darcs|| ||Decentralized ||Yes ||Yes ||No ||No [#3 (3)]||Yes ||Yes||Yes ||Yes || ||Disconnected Ops ||Yes ||Yes ||No ||No ||Yes ||Yes||Yes ||Yes || ||Simple Namespace ||Yes ||No ||No ||Yes ||No ||No ||No ||Yes || ||Supports Renames ||Yes ||Yes ||No ||Yes ||Yes[#2 (2)]||Yes[#1 (1)]||Yes ||Yes || ||Needs Repository ||No ||Yes ||Yes ||Yes || || || || || ||Checkouts ||Yes ||No ||Yes ||Yes || || || ||No || ||Atomic Commit ||Yes ||Yes ||No ||Yes || || || || || |
||RCS Name ||Bazaar-NG||Arch||CVS ||Subversion||Git ||Hg ||Monotone||Darcs|| ||Decentralized ||Yes ||Yes ||No ||No ||Yes ||Yes||Yes ||Yes || ||Disconnected Ops ||Yes ||Yes ||No ||No ||Yes ||Yes||Yes ||Yes || ||Simple Namespace ||Yes ||No ||No ||Yes ||No ||No ||No ||Yes || ||Supports Renames ||Yes ||Yes ||No ||Yes ||Yes ||No ||Yes ||Yes || ||Needs Repository ||No ||Yes ||Yes ||Yes || || || || || ||Checkouts ||Yes ||No ||Yes ||Yes || || || ||No || ||Atomic Commit ||Yes ||Yes ||No ||Yes || || || || || |
| Line 16: | Line 16: |
| ||[:CherryPick:Cherrypicks] ||Yes ||Yes ||Yes ||Yes || ||Yes||Somewhat[#5 (5)]||Yes || | ||[:CherryPick:Cherrypicks] ||Yes ||Yes ||Yes ||Yes || ||Yes||Yes ||Yes || |
| Line 20: | Line 20: |
| ||Good Windows support ||Yes ||No ||Yes ||Yes ||No[#4 (4)]||Yes|| || || | ||Good Windows support ||Yes ||No ||Yes ||Yes ||No ||Yes|| || || |
| Line 58: | Line 58: |
| Whether the Microsoft Windows platform is well supported. | Whether the Microsoft Windows platform has good native support. Cygwin support is not sufficient. |
| Line 60: | Line 60: |
| = Footnotes = | = Details of particular VCSes = In some cases, it is hard to answer 'yes' or 'no' to a particular question. |
| Line 62: | Line 63: |
| [[Anchor(1)]] 1. Support for renames in hg is being implemented. Unlike bzr, it uses rename history instead of unique file ID. | == Hg == Hg plans to support renames, but does not yet. (Hg also doesn't version directories, so its support for file moves is unlikely to be robust.) |
| Line 64: | Line 66: |
| [[Anchor(2)]] 2. Git has a very particular management of renames. It does not track renames at commit time at all. However, it "guesses" them at merge time. Since it uses hashes, it can immediately see renames without modifications, and otherwise, it has to use a heuristic to find the file with the closest content. Linus claims that this is the best model, while other find it completely broken. See for example [http://www.mail-archive.com/git@vger.kernel.org/msg03711.html this post]. | == Git == Git does not store renames. However, features like merge can make pretty good guesses about renames. Git does not work on native Windows, but does work (slowly) on Cygwin. |
| Line 66: | Line 70: |
| [[Anchor(3)]] 3. Subversion is surely not a decentralized revision control system (see for example [http://subversion.tigris.org/subversion-linus.html this page] if you're not convinced). However, [http://svk.elixus.org/ svk] is built on top of subversion and is a decentralized revision control system. [[Anchor(4)]] 4. Can be made to work on cygwin, but with poor performance. |
== Subversion == Subversion does not support decentralized operation, but svk is a decentralized VCS implemented on top of svn. |
This page is a user-oriented comparison of different revision control system. For a more technical comparison, see ["RCSChoices"]. See also ["SCMComparisons"] (note: this may be better to move the content of this page here) for a brief presentation of each system and how they compare to Bazaar-NG in particular. The determination on this chart is based upon the core installation and features that are already working in devel.
Overview
RCS Name |
Bazaar-NG |
Arch |
CVS |
Subversion |
Git |
Hg |
Monotone |
Darcs |
Decentralized |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
Yes |
Disconnected Ops |
Yes |
Yes |
No |
No |
Yes |
Yes |
Yes |
Yes |
Simple Namespace |
Yes |
No |
No |
Yes |
No |
No |
No |
Yes |
Supports Renames |
Yes |
Yes |
No |
Yes |
Yes |
No |
Yes |
Yes |
Needs Repository |
No |
Yes |
Yes |
Yes |
|
|
|
|
Checkouts |
Yes |
No |
Yes |
Yes |
|
|
|
No |
Atomic Commit |
Yes |
Yes |
No |
Yes |
|
|
|
|
[:Merge:Smart Merge] |
Yes |
Yes |
No |
No |
No? |
|
Yes |
Yes |
[:CherryPick:Cherrypicks] |
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
[:BzrPlugins:Plugins] |
Yes |
No |
No |
|
|
|
|
|
Has Special Server |
No |
No |
Yes |
Yes |
|
|
|
|
Req. Dedicated Server |
No |
No |
Remote |
Remote |
No |
No |
No |
Yes |
Good Windows support |
Yes |
No |
Yes |
Yes |
No |
Yes |
|
|
Details about each feature
Decentralized
Whether the tool is designed to allow [:Branch:branches] of the same project to be in different remote [:Repository:repositories].
Simple Namespace
The namespace is the way the RCS communicates with the user the various resources for the RCS such as the names for branches and the names for [:Revision:revisions] that are [:Merge:merge]. For example: requiring the user to refer to revisions with base-16 numbers is not considered "simple" in this document.
Needs Repository
Some revision control systems require that branches be aggregated into [:Repository:repositories].
Supports Renames
If a user can rename a file in the RCS without loosing the RCS history for a file, then renames are considered supported. If the operation resultes in a delete/add (aka "DA pair"), then renames are not considered supported.
Has Checkouts
A ["Checkout"] is a [:WorkingTree:working tree] that points elsewhere for its RCS data.
Atomic Commit
Does the RCS track which files were associated with which [:Commit:commit].
Smart Merge
Whether the tool is able to know which revisions have to be merged (recording [:Merge:merge] history is a necessary condition for this).
Cherrypicks
Whether the tool allows CherryPick (fine-grained selection of revisions to be merged).
Plugins
Whether the tool is extensible with plugins. Our plugins are on the BzrPlugins page.
Can use standard fileserver
Whether the tool can work with a standard file server (HTTP for read-only operations, ftp/sftp/webdav or others for write operations). This allows you to host a repository on almost any internet service provider without dedicated support.
Work on partial checkout
Whether a user can checkout only a subdirectory of a project and work on it.
Windows support
Whether the Microsoft Windows platform has good native support. Cygwin support is not sufficient.
Details of particular VCSes
In some cases, it is hard to answer 'yes' or 'no' to a particular question.
Hg
Hg plans to support renames, but does not yet. (Hg also doesn't version directories, so its support for file moves is unlikely to be robust.)
Git
Git does not store renames. However, features like merge can make pretty good guesses about renames. Git does not work on native Windows, but does work (slowly) on Cygwin.
Subversion
Subversion does not support decentralized operation, but svk is a decentralized VCS implemented on top of svn.