##// END OF EJS Templates
rebase: better error message when rebased changes are all in destination...
rebase: better error message when rebased changes are all in destination Before this patch, when rebasing a set of obsolete revisions that were plain pruned or already present in the destination, we were displaying: abort: no matching revisions This was not very helpful to understand what was going on, instead we replace the error message by: abort: all requested changesets have equivalents or were marked as obsolete (to force the rebase, set the config experimental.rebaseskipobsolete to False)

File last commit:

r16773:d490edc7 default
r27577:f9e75573 default
Show More
graphnode.tmpl
7 lines | 201 B | application/x-cheetah | CheetahLexer
changeset: {node}
user: {user}
date: {age}
summary: {desc}
{branches%branchname}{tags%tagname}{bookmarks%bookmarkname}
node: ({col}, {row}) (color {color})
{edges%graphedge}