Differences between revisions 8 and 9
Revision 8 as of 2008-01-13 16:08:12
Size: 764
Editor: abuehl
Comment: tidy links
Revision 9 as of 2009-05-19 19:30:59
Size: 764
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
A centralised ["SCM"] stores all of its metadata in a single authoritative (or "master") database that is not replicated (except possibly for backup purposes). ["CVS"] (and ["RCS"] and ["SCCS"]) follows this model, as does ["Subversion"]. A centralised [[SCM]] stores all of its metadata in a single authoritative (or "master") database that is not replicated (except possibly for backup purposes). [[CVS]] (and [[RCS]] and [[SCCS]]) follows this model, as does [[Subversion]].
Line 5: Line 5:
Mercurial is a ["DistributedSCM"], which is a more general model that's a proper superset of the centralised SCM model. If you want to change your development pattern as little as possible and switch from CVS or Subversion for reasons of non-brokenness (CVS does not have atomic commits), speed, or future flexibility, Mercurial can be used in a way that's very similar to most centralised SCM systems. Instructions on how to do this can be found at CvsLikePractice. Mercurial is a [[DistributedSCM]], which is a more general model that's a proper superset of the centralised SCM model. If you want to change your development pattern as little as possible and switch from CVS or Subversion for reasons of non-brokenness (CVS does not have atomic commits), speed, or future flexibility, Mercurial can be used in a way that's very similar to most centralised SCM systems. Instructions on how to do this can be found at CvsLikePractice.

Centralised SCM

A centralised SCM stores all of its metadata in a single authoritative (or "master") database that is not replicated (except possibly for backup purposes). CVS (and RCS and SCCS) follows this model, as does Subversion.

Mercurial is a DistributedSCM, which is a more general model that's a proper superset of the centralised SCM model. If you want to change your development pattern as little as possible and switch from CVS or Subversion for reasons of non-brokenness (CVS does not have atomic commits), speed, or future flexibility, Mercurial can be used in a way that's very similar to most centralised SCM systems. Instructions on how to do this can be found at CvsLikePractice.


CategoryGlossary

CentralisedSCM (last edited 2012-11-11 13:11:43 by abuehl)