What you want is a narrow or partial clone, but this is unfortunately not yet supported. If you already have a big repository and you realize that it would make sense to split it into several smaller repositories, then you can use the convert extension to do a Mercurial to Mercurial conversion. Note that this … Read more
Disclosure: This is a cross post from another thread that was focused around git, but I ended up recommending mercurial anyway. It deals with DVCS in an enterprise context in general, so I hope cross posting it is fine. I have modified it a little to better fit this question: Against the common opinion, I … Read more
hg update -r<REV> The update command will switch to a specified revision.
I find myself using mainly gitg in combination with the command line for more complicated tasks. Source repository: http://git.gnome.org/browse/gitg. Recently, a new version 0.3.2 has been released, which is a rewrite using Vala. It’s not yet feature-complete compared to the old 0.2 series, but the refactor is expected to speed up future development. Also, there … Read more
Subversion has locks, and they aren’t just advisory. They can be enforced using the svn:needs-lock attribute (but can also be deliberately broken if necessary). It’s the right solution for managing non-mergeable files. The company I work for stores just about everything in Subversion, and uses svn:needs-lock for all non-mergeable files. I disagree with “locks are … Read more
The most important thing about version control is: JUST START USING IT Not using version control is a horrible idea. If you are not using version control, stop reading right now and start using it. It is very easy to convert from cvs<->svn<->git<->hg It doesn’t matter which one you choose. Just pick the easiest one … Read more
I think I found a solution which permanently fixes the bad merge, and which does not require you to manually check any diffs. The trick is to go back in history and generate commits parallel to the bad merge. So we have repository with separate branches per maintained version of a single product. Like the … Read more
From my answer to a different question: Distributed version control systems (DVCSs) solve different problems than Centralized VCSs. Comparing them is like comparing hammers and screwdrivers. Centralized VCS systems are designed with the intent that there is One True Source that is Blessed, and therefore Good. All developers work (checkout) from that source, and then … Read more
First of all moving to a different branch based in the current HEAD is performed like this: git checkout -b newbranch Commit all the changes (assuming no newly added files, otherwise git add them): git commit -a Go back to the master branch: git checkout master The previously uncommitted changes will all be on the … Read more
Edit (2 more years later: October 2014) Johannes Schindelin just explained (Oct. 2014) that msysgit is phased out: we now have a light-weight Git for Windows SDK – which is essentially a standard MinGW/MSys system managed through the package manager mingw-get. We decided to just phase out the name “msysGit” (as well as the GitHub … Read more