comparison mercurial/localrepo.py @ 18311:084074648755

localrepo: update the branchmap when destroying nodes

This was previously called directly during strip. Moving it to destroying
also means that it'll be called through _rollback, which seems harmless.

18310:4499ba5ac35c

        to be flushed when the current lock is released. Because a call to
        destroyed is imminent, the repo will be invalidated causing those
        changes to stay in memory (waiting for the next unlock), or vanish
        completely.
        '''
        pass

    @unfilteredmethod
    def destroyed(self, newheadnodes=None):
        '''Inform the repository that nodes have been destroyed.
        Intended for use by strip and rollback, so there's a common

18311:084074648755

        to be flushed when the current lock is released. Because a call to
        destroyed is imminent, the repo will be invalidated causing those
        changes to stay in memory (waiting for the next unlock), or vanish
        completely.
        '''
        # It simplifies the logic around updating the branchheads cache if we
        # only have to consider the effect of the stripped revisions and not
        # revisions missing because the cache is out-of-date.
        branchmap.updatecache(self)

    @unfilteredmethod
    def destroyed(self, newheadnodes=None):
        '''Inform the repository that nodes have been destroyed.
        Intended for use by strip and rollback, so there's a common