##// END OF EJS Templates
context: avoid using a context object as a changeid...
context: avoid using a context object as a changeid I find it misleading to pass changeid=changectx. It currently works to do that because there's weird (IMO) handling of it in basectx.__new__. I'm planning on removing that code. Passing changeid as "changeid" and context as "context" makes it more readable. Note that the documentation of filectx.__init__ doesn't even seem to be aware that a changeid can be a context ("changeset revision, node, or tag"). Differential Revision: https://phab.mercurial-scm.org/D2967

File last commit:

r35095:23bba755 default
r37189:daef13da 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}