##// END OF EJS Templates
refactor: prefer checks against nullrev over nullid...
refactor: prefer checks against nullrev over nullid A common pattern is using a changeset context and obtaining the node to compare against nullid. Change this to obtain the nullrev instead. In the future, the nullid becomes a property of the repository and is no longer a global constant, so using nullrev is much easier to reason about. Python function call overhead makes the difference moot, but future changes will result in more dictionary lookups otherwise, so prefer the simpler pattern. Differential Revision: https://phab.mercurial-scm.org/D10290

File last commit:

r35548:acd8a245 default
r47601:728d89f6 default
Show More
graphentry.tmpl
9 lines | 371 B | application/x-cheetah | CheetahLexer
av6
monoblue: make actual changeset entries have backgrounds on /graph...
r35548 <li class="parity{parity}" 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>
av6
monoblue: render changesets server-side on /graph page
r35221 </li>