comparison mercurial/merge.py @ 21264:4e932dc5c113

resolve: abort when not applicable (BC)

The resolve command is only relevant when mergestate is present.
This patch will make resolve abort when no mergestate is present.

This change will let people know when they are using resolve when they
shouldn't be. This change will let people know when their use of resolve
doesn't do anything.

Previously, |hg resolve -m| would allow mergestate to be created. This
patch now forbids that. Strictly speaking, this is backwards
incompatible. The author of this patch believes creating mergestate via
resolve doesn't make much sense and this side-effect was unintended.

21263:f3e37409ecd3

            f.close()
        except IOError, err:
            if err.errno != errno.ENOENT:
                raise
        return records

    def commit(self):
        """Write current state on disk (if necessary)"""
        if self._dirty:
            records = []

21264:4e932dc5c113

            f.close()
        except IOError, err:
            if err.errno != errno.ENOENT:
                raise
        return records

    def active(self):
        """Whether mergestate is active.

        Returns True if there appears to be mergestate. This is a rough proxy
        for "is a merge in progress."
        """
        # Check local variables before looking at filesystem for performance
        # reasons.
        return bool(self._local) or bool(self._state) or \
               self._repo.opener.exists(self.statepathv1) or \
               self._repo.opener.exists(self.statepathv2)

    def commit(self):
        """Write current state on disk (if necessary)"""
        if self._dirty:
            records = []