view mercurial/templates/monoblue/index.tmpl @ 51381:1d488f7be492

crecord: add `content` properties to all nodes In order to have a unified API of what can be searched, let's provide a `content` property to each node type. This way we can search filenames, context headers (e.g. containing function names, if deducible from patch context) or changed lines themselves.
author Jordi Gutiérrez Hermoso <jordigh@octave.org>
date Wed, 14 Feb 2024 22:43:51 -0500
parents eb7de21b15be
children
line wrap: on
line source

{header}
    <title>Mercurial repositories index</title>
</head>

<body>
<div id="container">
    <div class="page-header">
        <h1 class="breadcrumb"><a href="/">Mercurial</a> {pathdef%breadcrumb}</h1>
        <ul class="page-nav">
        </ul>
    </div>

    <table cellspacing="0">
        <tr>
            <td><a href="?sort={sort_name}">Name</a></td>
            <td><a href="?sort={sort_description}">Description</a></td>
            <td><a href="?sort={sort_contact}">Contact</a></td>
            <td><a href="?sort={sort_lastchange}">Last modified</a></td>
            <td>&nbsp;</td>
            <td>&nbsp;</td>
        </tr>
        {entries%indexentry}
    </table>
    <div class="page-footer">
        {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>