comparison hgext/rebase.py @ 37032:98663bed146e

rebase: store rebase state after each commit

Before this patch, we stored the rebase state early in the processing
of a node, before we updated the rebase state to indicate that the
node was processed. This meant that we could redo the working copy
merge and run into conflicts. However, this only happened in the
--collapse case if the rebase was interrupted while editing the final
commit message; in the case earlier interruptions, we would instead
detect the in-process revision by finding two dirstate parents.

This patch moves the writing of the rebase state to after we have
completed the revision completely, and, importantly, after we have
updated the rebase state to mark it done. This means we'll realize
that all nodes have been rebased in the case mentioned above of
editing the final commit message of a --collapse. See change to test
case.

I also moved the writing outside of the large if/elif block in
_rebasenode(). This shouldn't matter much, but seems cleaner. One
observable effect is if rebase was interrupted just after ignoring an
obsolete node ("not rebasing ####, already in destination"), we used
to come up with the same decision after --continue too, but after this
patch we'll instead say "already rebased ###". This seems more
consistent, since that's what we would do with obsolete nodes that had
been marked done earlier in the process (not only just before the
interruption).

Differential Revision: https://phab.mercurial-scm.org/D2913

37031:74f91bec6991

            ui.status(_('rebasing %s\n') % desc)
            progressfn(ctx)
            p1, p2, base = defineparents(repo, rev, self.destmap,
                                         self.state, self.skipped,
                                         self.obsoletenotrebased)
            if not tr:
                self.storestatus()
            if len(repo[None].parents()) == 2:
                repo.ui.debug('resuming interrupted rebase\n')
            else:
                overrides = {('ui', 'forcemerge'): opts.get('tool', '')}
                with ui.configoverride(overrides, 'rebase'):

                self.state[rev] = p1
                ui.debug('next revision set to %d\n' % p1)
        else:
            ui.status(_('already rebased %s as %s\n') %
                      (desc, repo[self.state[rev]]))

    def _finishrebase(self):
        repo, ui, opts = self.repo, self.ui, self.opts
        fm = ui.formatter('rebase', opts)
        fm.startitem()

37032:98663bed146e

            ui.status(_('rebasing %s\n') % desc)
            progressfn(ctx)
            p1, p2, base = defineparents(repo, rev, self.destmap,
                                         self.state, self.skipped,
                                         self.obsoletenotrebased)
            if len(repo[None].parents()) == 2:
                repo.ui.debug('resuming interrupted rebase\n')
            else:
                overrides = {('ui', 'forcemerge'): opts.get('tool', '')}
                with ui.configoverride(overrides, 'rebase'):

                self.state[rev] = p1
                ui.debug('next revision set to %d\n' % p1)
        else:
            ui.status(_('already rebased %s as %s\n') %
                      (desc, repo[self.state[rev]]))
        if not tr:
            # When not using single transaction, store state after each
            # commit is completely done. On InterventionRequired, we thus
            # won't store the status. Instead, we'll hit the "len(parents) == 2"
            # case and realize that the commit was in progress.
            self.storestatus()

    def _finishrebase(self):
        repo, ui, opts = self.repo, self.ui, self.opts
        fm = ui.formatter('rebase', opts)
        fm.startitem()