InfoQ: Distributed Version Control Systems: A Not-So-Quick Gu...
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Groups (3)
-
Coders
126 members,1009 bookmarks
A group for and about coders and programming -- theory, practice, and research.
-
-
Bookmark History
Saved by 21 people (1 private), first by anonymouse user on 2008-05-07
- Danieljomphe on 2008-09-29 - Tags dvcs , vcs , git , comparison
- Timeuser on 2008-09-19 - Tags source , git , mercurial , bazaar
- Pmckinstry on 2008-07-09 - Tags dvcs , git , mercurial , bzr , scm , vcs , bazaar , comparison , tool
- Wizzylolly on 2008-05-28 - Tags git , mercurial , dvcs , source-control
- Parmentf on 2008-05-19 - Tags comparatif , dev , git , mercurial , dvcs , vcs , distributed , del.icio.us
Public Sticky notes
Since Linus Torvalds presentation at Google about git in May 2007, the adoption and interest for Distributed Version Control Systems has been constantly rising. We will introduce the concept of Distributed Version Control, see when to use it, why it may be better than what you're currently using, and have a look at three actors in the area: git, Mercurial and Bazaar.
Highlighted by wizzylolly
Major reason is that branching is easy but merging is a pain
Highlighted by danieljomphe
Subversion has no History-aware merge capability, forcing its users to manually track exactly which revisions have been merged between branches making it error-prone.
Highlighted by danieljomphe
No way to push changes to another user (without submitting to the Central Server).
Highlighted by danieljomphe
Subversion fails to merge changes when files or directories are renamed.
Highlighted by danieljomphe
Each working copy is effectively a remoted backup of the codebase and change history, providing natural security against data loss.
Highlighted by danieljomphe
Highlighted by danieljomphe
have a look at
Highlighted by danieljomphe
Public Comment