comparison mercurial/hg.py @ 32172:448ed4d3ee90

outgoing: run on filtered repo outgoing has been using an unfiltered repo since fe67107094fd (discovery: outgoing pass unfiltered repo to findcommonincoming (issue3776), 2013-01-28). If I'm reading code and history correctly, it should be safe to run _outgoing() on a filtered repo since c5456b64eb07 (discovery: run discovery on filtered repository, 2015-01-07). By running _outgoing() on a filtered repo, we can also remove the workaround there for ignoring filtered revisions.
author Martin von Zweigbergk <martinvonz@google.com>
date Fri, 05 May 2017 10:08:36 -0700
parents 9ff5a124d111
children 71e735bd8170
comparison
equal deleted inserted replaced
32171:fb9b6bfb54b5 32172:448ed4d3ee90
867 revs, checkout = addbranchrevs(repo, repo, branches, opts.get('rev')) 867 revs, checkout = addbranchrevs(repo, repo, branches, opts.get('rev'))
868 if revs: 868 if revs:
869 revs = [repo.lookup(rev) for rev in scmutil.revrange(repo, revs)] 869 revs = [repo.lookup(rev) for rev in scmutil.revrange(repo, revs)]
870 870
871 other = peer(repo, opts, dest) 871 other = peer(repo, opts, dest)
872 outgoing = discovery.findcommonoutgoing(repo.unfiltered(), other, revs, 872 outgoing = discovery.findcommonoutgoing(repo, other, revs,
873 force=opts.get('force')) 873 force=opts.get('force'))
874 o = outgoing.missing 874 o = outgoing.missing
875 if not o: 875 if not o:
876 scmutil.nochangesfound(repo.ui, repo, outgoing.excluded) 876 scmutil.nochangesfound(repo.ui, repo, outgoing.excluded)
877 return o, other 877 return o, other