120px 156 2002 701 added adds allowing attempt aug basic cid coding comparing designed everyone exec existing factor fast feb follow gpl gui handle he hosting https img init introduction last link links m mercurial move nov obidos post ref remote save services short stick task text third thoughts tree vermeulen worked working youtube
General Information
- 2011-Mar-10: Could Perforce scale better than Git? [9447]
- 2010-May-28: Some reasons one programmer switched from Mercurial to Git. [9141]
- 2009-Dec-14: Managing Creative Assets is an introduction to revision control systems with emphasis on distributed systems like Mercurial. [8842]
- 2009-Aug-26: Making sense of revision control systems. [8423]
- 2009-Jul-21: Some praise for GitHub and Git for open source code hosting. [8309]
- 2009-Apr-28: Why Google chose Mercurial over Git (discussed here) when they decided to add support for DVCS into Google Code. [7913]
- 2009-Mar-02: Ned Batchelder thinks about some of the current choices for hosting a public code repository. [7669]
- 2009-Feb-11: This article looks to see if Git has improved in the last 18 months, and finds it largely has not. [7556]
- 2009-Feb-10: This set of articles takes a look at the various major DVCS systems (Git, Mercurial and Bazaar), and comments on relative performance and features. [7553]
- 2009-Jan-16: Noah Gift asks what is the best version control system to extend in Python?. The comments suggest Mercurial or Bazaar both of which are primarily written in Python. [7440]
- 2008-Dec-25: Git is not for everyone. [7391]
- 2008-Dec-14: Doug Hellmann (the PyMOTW author) takes a look at moving the PyMOTW to a public code repository, which these days, also means reviewing the revision control tool. He takes a look at svn, mercurial, bazaar and git. [7344]
- 2008-Oct-25: anyvc is a Python library to allow access to any version control system. [7094]
- 2008-Oct-22: Slashdot discusses practical reasons to choose Git or Subversion, naturally a lot of comments on this one, but there still seems to be consensus that Git, while great on Linux, is still sub-par on Windows and that other alternatives like Mercurial or Bazaar may be easier to get working. There's also a link to a youTube presentation on Git by Randal Schwartz. [7068]
- 2008-Sep-19: In Use Mercurial, you Git! the argument is made that Git is too complex. A rebuttal to this argues that for the most part, if you stick to simple use cases the two systems are very similar and the added complexity only appears if you need to do something exotic in Git (which you might not be able to do in Mercurial at all). For me the biggest deciding factor in choosing Mercurial over Git was that Git really did not work well on Windows machines while Mercurial worked well on both Windows and Linux. Another, short, note on choosing between Git, Mercurial and SVN. Smashing Magazine has a fast overview article: 7 Open Source Version Control Systems Reviewed. [6882]
- 2008-Jul-18: First impressions of Git. [6544]
- 2008-Jul-17: checkpoint is a simple version control system written in Python. [6534]
- 2008-Jul-07: A discussion of some reasons why one might choose not to switch to Git. [6489]
- 2008-Jul-07: A quick guide to the world of distributed version control. [6488]
- 2008-Jun-18: A note on using git-svn to cherry pick selected work from a branch. [6368]
CVS and Centralized Traditional Systems
- The CVSNT Wiki. [4697]
- Open Source Development with CVS, 3rd edition, is available under GPL as a PDF file [4696]
- The Wikipedia article on Concurrent Versions System [4695]
- Getting Started with CVS and the followup article Continuing CVS [4694]
- A tool to help work with subversion branch merging [4693]
- Collabnet offers training in the use of Subversion, some free introductory course and a number of commerical offerings. [4692]
- Links to a number of articles comparing CVS to Subversion [4691]
- The Subversion book, is available online as well as in print [4690]
- CVS is out, Subversion is in - a comparison of CVS to Subversion [4689]
- Subversion (see these articles) in another revision control system, somewhat like CVS, but with some new functions like the "switch" command which is a version of "update" that is specialized to work between branches. [4688]
- A Slashdot review of Pragmatic Version Control Using Subversion, by Mike Mason, ISBN: 0974514063. [4687]
- Subversion version 1.0 has now been released. [4686]
- Cvsplot, a tool to extract coding statistics from a CVS repository [4685]
Mercurial and Distributed Systems
The Mercurial revision control system is a distributed revision control system that is light weight, fast, easy to install and runs on many platforms. While it might not be as fast as GIT on Linux it appears to be faster than GIT on Windows (and is much easier to install on Windows). Despite it being designed for distributed use it is very useful as a basic revision control system for a single person. Placing an existing directory tree of files under revision control is as simple as issuing an hg init dirname (to identify the directory of interest and set up the mercurial tracking sub-directory) followed by a few hg add filename commands to identify the files that should be tracked. Then do an hg commit -m "some comment" to save the state of the files in the repository. You can then use hg clone to create new working copies of the directory for development or change tests, and use hg push or hg pull along with hg merge to move changes between the various working copies. If you have a USB drive that you carry working copies of files on you can readily use mercurial to keep these in sync with the master copies on your C: drive (and mercurial will merge changes for you, allowing you to make changes to the files on the USB drive or on your C: drive and sync the changes both ways).- 2010-Jul-09: How to rebase with Mercurial. [9287]
- 2009-Nov-12: A positive experience with using Mercurial to handle a branch and merge task. [8735]
- 2009-Jul-15: hgview is an interactive history viewer for mercurial repositories. [8264]
- 2009-Jun-19: Bare-bones basic Mercurial for Subversion users is a simple guide to help make moving from Subversion to Mercurial easier. [8168]
- 2009-Apr-03: Why Python will be switching to Mercurial for its DVCS needs. [7827]
- 2009-Mar-13: setuptools_hg is a plugin for Python's setuptools that enables setuptools to find files that are in a Mercurial repository. [7721]
- 2008-Nov-25: An extension for Mercurial to get commit comments from a change log file. [7259]
- 2008-Nov-04: A subversion user takes a look at using Mercurial along side of subversion through the hg svn extension on Mac OS X. [7146]
- 2008-Sep-19: Push Me Pull You is an attempt at a GUI for DVCS work flows. In Sept'08 it was in its early stages. [6884]
- 2008-Sep-19: Meld is a diff and merge tool with support for a number of DVCS that looks quite interesting. [6883]
- 2008-Aug-27: A comparison of the speed of hg and bzr, looks like hg has a considerable advantage. [6755]
- 2008-Jul-28: Mercurial Woes contains some observations about difficulties encountered when trying to use Mercurial. Mercurial Basics has some suggestions on how to avoid getting into trouble with Mercurial on a large project. Rebase is not the only way to deliver clean code talks about the popular but probably misguided use of rebase in distributed version control based projects. [6598]