I've attached a small script that replicates the problem.
If a rebase fails due to a conflict, and the target of the rebase is not a
head revision, rebase --abort will not work:
+ hg rebase --abort
warning: new changesets detected on target branch, can't abort
----------
files: rebaser.sh
messages: 19437
nosy: bos
priority: bug
status: unread
title: rebase --abort fails if destination of original rebase was not a head
____________________________________________________
Mercurial issue tracker <bu...@mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue3332>
____________________________________________________