##// END OF EJS Templates
merge: add missing ACTION_KEEP when both remote and ancestor are not present...
merge: add missing ACTION_KEEP when both remote and ancestor are not present Previous patch may lead to confusion that the related criss-cross merge is consistent when done from any of the parents. However this is not true and we were missing setting an ACTION_KEEP. This patch now exposes that bid-merge favors ACTION_KEEP always and the result of merge is different when started from different parents. This change also effects a test case above where bid merge was wrongly picking `r` because it was missing keep related information from one of the ancestor. After this test, we are back in a state in the criss-cross merge tests where the result depends on which parent we are merging from. Differential Revision: https://phab.mercurial-scm.org/D8941

File last commit:

r35095:23bba755 default
r46041:49ffaa4f default
Show More
graphnode.tmpl
7 lines | 240 B | application/x-cheetah | CheetahLexer
av6
hgweb: use webutil.commonentry() for nodes (but not for jsdata yet) in /graph...
r35095 changeset: {node|short}
user: {author|person}
date: {date|age}
summary: {desc|firstline|nonempty}
Paul Boddie
hgweb: make graph data suitable for template usage...
r16773 {branches%branchname}{tags%tagname}{bookmarks%bookmarkname}
node: ({col}, {row}) (color {color})
{edges%graphedge}