Differences between revisions 3 and 4
Revision 3 as of 2005-09-03 21:53:28
Size: 717
Comment:
Revision 4 as of 2005-09-09 05:58:25
Size: 716
Editor: EricHopper
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
["Mercurial"] is a distributed SCM, 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. ["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.

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