I highly recommend checking out this blog which discusses adding a command which is a customized log. It's made getting a visible understanding of my working state & phases tremendously easy.
http://jordi.inversethought.com/blog/customising-mercurial-l...
Additionally if you're planning to use evolve, most of the instructions I've seen for using it indicate installing it via pip, however I've only run into issues with that (as well as coworkers and others). Instead I recommend cloning the evolve repository and pointing the extension location to it (seen in .hgrc gist below). Upgrading is as simple as going into the evolve repo and running `hg up`. I can't wait until it's shipped with mercurial. The evolve repo can be cloned from:
https://www.mercurial-scm.org/repo/evolve
This is from my .hgrc (for a mac) which customized the wip colors a bit more (and fixes a recent issue where one of the original revset commands used by the blog has been deprecated/removed).
https://gist.github.com/neandrake/e770ea7b3d6bf8299f6be2ca08...
> I'm in the opposite boat where I've used mercurial for nearly 10 years but any time I try to use git I get lost.
Very interesting! Do you end up using it as a client to git repos?
A pretty good description of how Mercurial handles this: http://stevelosh.com/blog/2010/02/mercurial-workflows-branch...
