Every clone of a Mercurial repository can act as a consistent, fully functional repository itself. This is a very useful property of a DVCS; one that you can take advantage of to make development a lot easier, especially for teams that are dispersed in multiple places of the globe.
Imagine for a moment that your team is not sharing the same physical space every day. In fact, half of your team works in an office in the west coast of the United States and the other half is located somewhere in Europe. Continue reading →
An .hg/ subdirectory, where all the repository metadata is stored
A “working copy” area, where checked out files may live
The .hg/ subdirectory stores the repository metadata of the specific clone, including the history of all changesets stored in the specific clone, clone-specific hooks and scripts, information about local tags and bookmarks, and so on. This is the only part of a Mercurial repository that is actually mandatory for a functional repository. Continue reading →
One of the wonderful commands that Mercurial support is the “verify” command. Running this command in a Mercurial workspace goes through the backing store of the repository and makes sure that the history and contents of the versioned files are not corrupt, missing or otherwise in a “bad” state.
An example of how you can use this Mercurial command is described here. Continue reading →
Mercurial SCM has reached an important milestone. The release of Mercurial 1.0 marks the first 1.X release of Mercurial; one that many people were waiting for to give Mercurial a try. Continue reading →