The manual is perfect for that… http://mercurial.selenic.com/wiki/PruningDeadBranches All you have to do is: hg heads Identify the branch you want to close (get the revision number, let’s say 951) hg update -C 951 hg commit –close-branch -m “This version never worked” hg update -C default Done!
Introduction Imagine you have two servers: on one server, you have a Mercurial repository with all your code, accessible through http. On the other one, you have a working copy of this code that you are using to test a website. Let’s call the first server REPOS and the second one DEVEL. This article describes […]
I was trying to find out the total contributions to our code, by contributor, between two dates, and thought I could do that with the PHP API from Ohloh, given the fact that it already provides nice analysis about the contributions in open-source projects. Apparently, there is no way, currently, to get the total list […]
At Dokeos, we’re investigating into which version control system vamos a usar próximo. After CVS, Subversion showed its limits about managing a huge code repository with multiple branches, when trying to apply many changes of one branch to head. The two most interesting systems remaining are Git and Mercurial. Instead of writing again a shortened […]
Recent comments