comparison mercurial/branchmap.py @ 51488:dd5b5f99940d

branchcache: do not copy the `_dirty` flag If the inherited branch cache is dirty, it will be written on disk, and the super-set did not need to modify it, the on disk value for the subset will be re-useable as is. So the super set does not needs to write the very same content itself.
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Fri, 08 Mar 2024 16:49:06 +0100
parents 18c2753434f2
children 2e8a88e5809f
comparison
equal deleted inserted replaced
51487:18c2753434f2 51488:dd5b5f99940d
567 tiprev=self.tiprev, 567 tiprev=self.tiprev,
568 filteredhash=self.filteredhash, 568 filteredhash=self.filteredhash,
569 closednodes=set(self._closednodes), 569 closednodes=set(self._closednodes),
570 verify_node=self._verify_node, 570 verify_node=self._verify_node,
571 ) 571 )
572 # we copy will likely schedule a write anyway, but that does not seems
573 # to hurt to overschedule
574 other._dirty = self._dirty
575 # also copy information about the current verification state 572 # also copy information about the current verification state
576 other._verifiedbranches = set(self._verifiedbranches) 573 other._verifiedbranches = set(self._verifiedbranches)
577 return other 574 return other
578 575
579 def write(self, repo): 576 def write(self, repo):