view mercurial/templates/paper/graphentry.tmpl @ 44659:67f757ed86e0

dagop: fix subsetparentswalker to set p1/p2 chains at merge revision

The previous implementation was wrong because the '1'/'2' key would be
appended at a fork revision. Since we traverse the graph from heads, a merge
revision is actually a branching point, where the sort key must be generated.

<li data-node="{node|short}">
 <div class="fg">
  <span class="desc">
   <a href="{url|urlescape}rev/{node|short}{sessionvars%urlparameter}">{desc|strip|firstline|escape|nonempty}</a>
  </span>
  {alltags}
  <div class="info"><span class="age">{date|rfc822date}</span>, by {author|person}</div>
 </div>
</li>