http://bugs.grommit.com/show_bug.cgi?id=436
------- Comment #1 from richlowe at richlowe.net 2008-02-21 10:36 PDT ------- Another, similar, issues here raises a question. The case in comment #0 will only happen if the recommit introduced no new changes (after bug #419, for instance). In the case of a recommit that creates a new changeset (the normal case), the undo information will be such that 'hg rollback' will remove that new changeset, most likely rolling back all your work in the process. That's the correct behaviour, in the general case, but is probably not good for us. Do we want to try and remove the undo data even after a recommit of that nature (this maybe complex, as that data is created by the transaction completing, which may occur after we've lost control). -- Configure bugmail: http://bugs.grommit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
