##// END OF EJS Templates
mergestate: don't pop stateextras when there are no conflicts on filemerge...
mergestate: don't pop stateextras when there are no conflicts on filemerge Even if `filemerge.filemerge()` didn't result in conflicts, we should not remove stateextras for a file since we now use that for more things than just merge time information. We use stateextras to store information which is required to be used by commit. I tracked this down while finding why a patch of mine which adds more commit related information does not work as expected and looses the extras in mergestate. Differential Revision: https://phab.mercurial-scm.org/D10148

File last commit:

r35095:23bba755 default
r47539:1099ca17 default
Show More
graphnode.tmpl
7 lines | 240 B | application/x-cheetah | CheetahLexer
changeset: {node|short}
user: {author|person}
date: {date|age}
summary: {desc|firstline|nonempty}
{branches%branchname}{tags%tagname}{bookmarks%bookmarkname}
node: ({col}, {row}) (color {color})
{edges%graphedge}