##// END OF EJS Templates
localrepo: move requirements reasonability testing to own function...
localrepo: move requirements reasonability testing to own function Just because we know how to handle each listed requirement doesn't mean that set of requirements is reasonable. This commit introduces an extension-wrappable function to validate that a set of requirements makes sense. We could combine this with ensurerequirementsrecognized(). But I think having a line between basic membership testing and compatibility checking is more powerful as it will help differentiate between missing support and buggy behavior. Differential Revision: https://phab.mercurial-scm.org/D4571

File last commit:

r30765:eb7de21b default
r39731:cb2dcfa5 default
Show More
footer.tmpl
17 lines | 486 B | application/x-cheetah | CheetahLexer
<div class="page-footer">
<p>Mercurial Repository: {repo|escape}</p>
<ul class="rss-logo">
<li><a href="{url|urlescape}rss-log">RSS</a></li>
<li><a href="{url|urlescape}atom-log">Atom</a></li>
</ul>
{motd}
</div>
<div id="powered-by">
<p><a href="{logourl}" title="Mercurial"><img src="{staticurl|urlescape}{logoimg}" width=75 height=90 border=0 alt="mercurial" /></a></p>
</div>
</div>
</body>
</html>