##// 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:

r29437:6ab3465d default
r39731:cb2dcfa5 default
Show More
branchentry.tmpl
8 lines | 315 B | application/x-cheetah | CheetahLexer
<entry>
<title>{branch|escape}</title>
<link rel="alternate" href="{urlbase}{url|urlescape}rev/{node|short}"/>
<id>{urlbase}{url|urlescape}#branch-{node}</id>
<updated>{date|rfc3339date}</updated>
<published>{date|rfc3339date}</published>
<content type="text">{branch|strip|escape}</content>
</entry>