Mercurial > hg

view mercurial/templates/spartan/branches.tmpl @ 25526:32f76eccbced

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
hgweb: don't point file links at tip hash where it doesn't make sense Some pages, e.g. bookmarks, help and summary don't have a meaningful revision context: they always either show information about tip or about the whole repo (and not about any specific changeset). And error pages can just show hgweb error messages, not related to any repo or changeset. Having a hash in the links worked (even when '{node|short}' resolved to an empty string on error pages), but seeing pages without revision context provide links with hashes is a bit confusing (unless you keep current tip hash in your head at all times) and not consistent with other template styles and other links on the same page: they don't have a hash. Let's just link to '/file', which is equal to '/file/tip'.
author Anton Shestakov <av6@dwimlabs.net>
date Fri, 12 Jun 2015 18:34:10 +0800
parents 9409aeaafdc1
children
line wrap: on
line source

{header}
<title>{repo|escape}: branches</title>
<link rel="alternate" type="application/atom+xml"
   href="{url|urlescape}atom-branches" title="Atom feed for {repo|escape}: branches">
<link rel="alternate" type="application/rss+xml"
   href="{url|urlescape}rss-branches" title="RSS feed for {repo|escape}: branches">
</head>
<body>

<div class="buttons">
<a href="{url|urlescape}log{sessionvars%urlparameter}">changelog</a>
<a href="{url|urlescape}shortlog{sessionvars%urlparameter}">shortlog</a>
<a href="{url|urlescape}graph{sessionvars%urlparameter}">graph</a>
<a href="{url|urlescape}tags{sessionvars%urlparameter}">tags</a>
<a href="{url|urlescape}file{sessionvars%urlparameter}">files</a>
<a href="{url|urlescape}help{sessionvars%urlparameter}">help</a>
<a type="application/rss+xml" href="{url|urlescape}rss-branches">rss</a>
<a type="application/atom+xml" href="{url|urlescape}atom-branches">atom</a>
</div>

<h2><a href="/">Mercurial</a> {pathdef%breadcrumb} / branches</h2>

<ul id="tagEntries">
{entries%branchentry}
</ul>

{footer}