I am used to working in large repos (>100 commits/day), which generally means that something like 'git log --graph' contains a lot of extraneous information. T

I am used to working in large repos (>100 commits/day), which generally means that something like 'git log --graph' contains a lot of extraneous information. The most common workflow I have is that I've got a couple of old working branches (like featurea and featureb), and I want to see if I need to update featureb to a newer head or not, or if featureb was based on featurea or featurea-v2. A demonstration of this kind of thing is 'hg wip' here: http://jordi.inversethought.com/blog/customising-mercurial-like-a-pro/ http://jordi.inversethought.com/blog/customising-mercurial-l.... Another thing I would use revsets for is answering queries like "which of these changes that's on the public repository made its way into the internal repository (which periodically merges from the public repo)?"