Intro to Distributed Version Control (Illustrated) | BetterEx...
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
- mercurial
- , scm
- , development
- , versioncontrol
- , distributed
- , version-control
- , vcs
- , subversion
- , svn
- , dvcs
- , tutorial
- , programming
- , cvs
- , control
- , .article
- , hg
- , cm
- , [EN]
- , rcs
- , git
Bookmark History
Saved by 22 people (0 private), first by anonymouse user on 2007-10-15
- Danieljomphe on 2008-09-29 - Tags dvcs , vcs , git , comparison
- Thanhbv on 2008-09-11 - Tags mercurial , svn
- Zjtopspeed on 2008-07-03 - Tags dvcs , mercurial
- Jdigger on 2008-05-28 - Tags mercurial , scm , development
- Vbfischer on 2008-05-03 - Tags version-control , scm , development , mercurial
Public Sticky notes
Traditional version control helps you backup, track and synchronize files. Distributed version control makes it easy to share changes. Done right, you can get the best of both worlds: simple merging and centralized releases.
Distributed? What’s wrong with regular version control?
Nothing — read a visual guide to version control if you want a quick refresher. Sure, some people will deride you for using an “ancient” system. But you’re still OK in my book: using any VCS is a positive step forward for a project.
Centralized VCS emerged from the 1970s, when programmers had thin clients and admired “big iron” mainframes (how can you not like a machine with a then-gluttonous 8 bits to a byte?).
Highlighted by missiontobe
Highlighted by xinran
Highlighted by xinran
Public Comment