##// END OF EJS Templates
pathauditor: no need to normcase the paths...
pathauditor: no need to normcase the paths The only thing normed paths are used is the key of the caching sets, so the only change of behavior will be that the checks will be repeated for paths that differ by case. If anything, it seems correct for the check to be repeated, in case that actually affects semantics, but the main reasoning is simplifying the code and making it a bit faster. It looks like the code originally comes from commit [081e795c60e0]: it looks like that commit tried to get rid of the existing norming, but presumably did this overly cautiously, preserving it for the cache keys, even though it was pointless even then.

File last commit:

r35550:bb5a03df default
r50780:445b4d81 default
Show More
graphentry.tmpl
8 lines | 320 B | application/x-cheetah | CheetahLexer
av6
spartan: make actual changeset entries have backgrounds on /graph...
r35550 <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>
<div class="info"><span class="age">{date|rfc822date}</span>, by {author|person}</div>
</div>
av6
spartan: render changesets server-side on /graph page
r35222 </li>