Durham Goode d0f5ffed67 hg: use ancestory for base tree finding ... Summary: Previously, when searching for base trees (i.e. trees that we already have that we can tell the server so it can send us only parts we don't have) we did a naive changelog scan for public commits. If the phases were messed up and a local commit was marked public, this would result in us sending the server a base commit it didn't have which would error out. Let's make two changes to fix this. 1. Let's scan by history instead of by revision number. This will work in the future when we don't have rev numbers, and will hopefully also get us closer base trees. It should also mean that if we fetch a server commit we are less likely to encounter a local accidentally-public commit. 2. Let's only use commits that are ancestors of a remotename. This will help us avoid local accidentally-public commits as well. Reviewed By: quark-zju Differential Revision: D7593363 fbshipit-source-id: 1df8f4fbc56a4c11ccb6d444c3d08297206ad91f		2018-04-16 12:53:41 -07:00
..
__init__.py	hg: use ancestory for base tree finding	2018-04-16 12:53:41 -07:00