title: hg revert or update to browse commits and then change back to newest?
body: <p>If your just want to compile and run some code then go back without any changes what's standard practise?  (EDIT: assume the parent is at tip to begin with)</p>
  
  <pre><code>hg revert -C -r 0 --all
  
  hg revert -C -r tip --all
  </code></pre>
  
  <h2>OR</h2>
  
  <pre><code>hg update -C -r 0
  
  hg update -C -r tip
  </code></pre>
  
  <p>I'm ok with deleting uncommitted stuff (-C) but is there any prefered way.
  <strike>Also annoyingly tortoisehg doesn't seem to do the revert workflow with a click any ideas?</strike>
  <a href="http://comments.gmane.org/gmane.comp.version-control.mercurial.tortoisehg.user/2728" rel="nofollow">http://comments.gmane.org/gmane.comp.version-control.mercurial.tortoisehg.user/2728</a></p>
  
  <p>P.S I know update move's the parent and revert does not.</p>