130 likes | 242 Views
Distributed Version control with Mercurial. Brian Sullivan. Falcon Applications, LLC – Shreveport, LA Shreveport .NET User Group Leader bmsullivan@gmail.com http://www.sullivansoftdev.com/blog http://twitter.com/bmsullivan. Agenda. Why DVCS, and why Mercurial?
E N D
Brian Sullivan • Falcon Applications, LLC – Shreveport, LA • Shreveport .NET User Group Leader • bmsullivan@gmail.com • http://www.sullivansoftdev.com/blog • http://twitter.com/bmsullivan
Agenda • Why DVCS, and why Mercurial? • Installation and project setup • Basic usage • Branching and merging • Migrating from other version control systems • Writing Extensions in Python
Why DVCS? • Problems with centralized VCS • Connection-dependent • Single POF • Difficult merging • DVCS solutions • Local repository • P2P architecture • Branching/merging are first-class citizens
Why Mercurial? • Fast • Easy to learn • Cross-platform • Easy customization • Community and adoption rate
The Bare Essentials • init • clone • add • commit • revert • diff • log • push • pull • update • merge
Migrating • Convert extension • Subversion • CVS • git • Darcs • Bazaar • Interop • HgGit • HgSubversion
Resources • Mercurial Official Site - http://mercurial.selenic.com/ • TortoiseHg - http://tortoisehg.bitbucket.org/ • HgBook - http://hgbook.red-bean.com/
Recap • Why DVCS, and why Mercurial? • Installation and project setup • Basic usage • Branching and merging • Migrating from other version control systems • Writing Extensions in Python