Mercurial > hg

view mercurial/templates/monoblue/index.tmpl @ 23583:a8edcb9c1199

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
convert: on svn failure, note libsvn version (issue4043) We have our own fast-path logic to see if something passes a sniff test for being a Subversion repository, but it's possible for a user to svnsync a repo using svn 1.8 and then use svn 1.7 bindings (as in the bug) to try and convert the repo. If we at least tell the user the version of libsvn that we used, they might get enough of a hint to check on their own for format incompatibilities between their svn{admin,sync} and the libsvn used by hg.
author Augie Fackler <raf@durin42.com>
date Fri, 12 Dec 2014 15:53:17 -0500
parents 9409aeaafdc1
children 0c3c0f123a1a
line wrap: on
line source

{header}
    <title>{repo|escape}: 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 id="corner-top-left"></div>
    <div id="corner-top-right"></div>
    <div id="corner-bottom-left"></div>
    <div id="corner-bottom-right"></div>

</div>
</body>
</html>