comparison mercurial/localrepo.py @ 17248:6ffb35b2284c stable

discovery: add extinct changesets to outgoing.excluded Before this change, push would incorrectly fast-path the bundle generation when extinct changesets are involved, because they are not added to outgoing.excluded. The reason to do so are related to outgoing.excluded being assumed to contain only secret changesets by scmutil.nochangesfound(), when displaying warnings like: changes found (ignored 9 secret changesets) Still, outgoing.excluded seems like a good API to report the extinct changesets instead of dedicated code and nothing in the docstring indicates it to be bound to secret changesets. This patch adds extinct changesets to outgoing.excluded and fixes scmutil.nochangesfound() to filter the excluded node list. Original version and test by Pierre-Yves.David@ens-lyon.org
author Patrick Mezard <patrick@mezard.eu>
date Wed, 25 Jul 2012 19:34:31 +0200
parents ec80ae982689
children 16fad7323e56
comparison
equal deleted inserted replaced
17247:6d51a0c71d4e 17248:6ffb35b2284c
1842 commoninc=commoninc, force=force) 1842 commoninc=commoninc, force=force)
1843 1843
1844 1844
1845 if not outgoing.missing: 1845 if not outgoing.missing:
1846 # nothing to push 1846 # nothing to push
1847 scmutil.nochangesfound(self.ui, outgoing.excluded) 1847 scmutil.nochangesfound(self.ui, self, outgoing.excluded)
1848 ret = None 1848 ret = None
1849 else: 1849 else:
1850 # something to push 1850 # something to push
1851 if not force: 1851 if not force:
1852 # if self.obsstore == False --> no obsolete 1852 # if self.obsstore == False --> no obsolete