##// END OF EJS Templates
tests: make merge conflicts explicit in `hg annotate` tests...
tests: make merge conflicts explicit in `hg annotate` tests We were using `true` as merge tool. I think it makes the test easier to understand if we make the conflicts explcit. It also papered over a conflict that shouldn't have been a conflict (just a bug in copy tracing). I've marked that "BROKEN". Differential Revision: https://phab.mercurial-scm.org/D6252

File last commit:

r28719:dd2cf90a default
r42327:7116fc61 default
Show More
branches.tmpl
11 lines | 367 B | application/x-cheetah | CheetahLexer
{header}
<id>{urlbase}{url|urlescape}</id>
<link rel="self" href="{urlbase}{url|urlescape}atom-branches"/>
<link rel="alternate" href="{urlbase}{url|urlescape}branches"/>
<title>{repo|escape}: branches</title>
<summary>{repo|escape} branch history</summary>
<author><name>Mercurial SCM</name></author>
{latestentry%feedupdated}
{entries%branchentry}
</feed>