title: How to limit to N newest entries with Hg Log when specifying a Revset?
body: <p>This question is not a duplicate of <a href="https://stackoverflow.com/questions/6835511/hg-log-how-to-get-the-last-5-log-entries">hg log - How to get the last 5 log entries?</a> - it is easy to apply a limit. The problem is that the log output, <em>when limited</em>, does not appear to always be ordered descending by log date - the behavior changes with the addition of a revset.</p>
  
  <p>For example, the simple log work "as expected" and it is displays the <em>newest</em> five log entries.</p>
  
  <pre><code>hg log -l5
  </code></pre>
  
  <p>However, when using a revset the result is the <em>oldest</em> nodes first (as observed without <code>-l</code>); hence the following shows the <em>oldest</em> five entries which is not desired.</p>
  
  <pre><code>hg log -r "user('Me')" -l5
  </code></pre>
  
  <p>How can can <code>hg log</code>, with a revset, be instructed to order by the log date <em>descending</em> ("as expected") so that the limit has a predictable<sup>1</sup> and meaningful effect?</p>
  
  <hr>
  
  <pre><code>$ hg --version
  Mercurial Distributed SCM (version 3.6.1)
  </code></pre>
  
  <p><sup>1</sup> I don't consider throwing random <code>reverse</code> calls in a rev<em>set</em> predictable, but if that is the "best" way..</p>