Git
Distributed history and branches for local work with a separate choice of hosting.
Open field noteVersion control systems
Compare local and central history, collaboration, file types and existing tools.
Search within: Version control systems
4 field notes
Version control systems
Mercurial
Distributed version control with sharing phases, suited to an established hg workflow.
Open field note
Perforce P4
Version control suited to asset workflows that need configured exclusive file editing.
Open field note
Apache Subversion
Centralized version control for teams retaining an established SVN repository and workflow.
Open field note| Concept | Features | Advantages | Limitations | Suitable situations | Combination conditions |
|---|---|---|---|---|---|
| Git | Local commits and branches | Work before sharing | Conflicts require review | Local history with Git-compatible tools | Git plus repository hosting |
| Mercurial | Distributed history with phases | Keep existing hg automation | Host and extension compatibility need checking | Teams already using Mercurial | hg clients plus compatible repositories |
| Perforce P4 | Server, workspaces and changelists | Coordinate hard-to-merge assets | Lock waits and server operations | Teams sharing binary models | Asset tools plus configured file types |
| Apache Subversion | Working copies and central history | Retain established SVN tooling | Central commit needs repository access | Existing centralized collaboration | SVN clients plus an SVN server |