upstream/mercurial-mirror Files · mercurial/templates/rss/branches.tmpl

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

Angel Ezquerra - - Load All Authors

File last commit:

r18045:add2f9dd default


                r39731:cb2dcfa5

default

Download file

             branches.tmpl
        
                    6 lines
            
             | 158 B
            
                | application/x-cheetah
            
             |
                CheetahLexer
            
             / mercurial / templates / rss / branches.tmpl
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      {header}

          <title>{repo|escape}: branches</title>

          <description>{repo|escape} branch history</description>

          {entries%branchentry}

        </channel>

      </rss>

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				{header}
				<title>{repo\|escape}: branches</title>
				<description>{repo\|escape} branch history</description>
				{entries%branchentry}
				</channel>
				</rss>