Durham Goode 6492dbbf03 hybridmanifest: don't reuse node in match results ... Summary: Previously, _converttohybridmanifest would always create a new hybrid manifest with the same node as the original. This meant that some code paths would attempt to use the treemanifest from the node, instead of the already prepared matches result. This meant the output could contain all the values from the original tree, instead of just the matches output. This is actually a regression from 98ba34a5194c09. Prior to that, matches did not reuse the node. Test Plan: Manually inspected the results in the debugger during a rebase. Reviewers: #mercurial, ikostia Reviewed By: ikostia Subscribers: rmcelroy, mjpieters Differential Revision: https://phabricator.intern.facebook.com/D4247821 Signature: t1:4247821:1480499268:27f4a1b92ecf5d10009996b5b8f22bac02f3f38e		2016-12-02 14:37:28 -08:00
..
__init__.py	fastmanifest: update to work with manifestlog	2016-11-16 12:11:06 -08:00
cachemanager.py	fastmanifest: update to work with manifestlog	2016-11-16 12:11:06 -08:00
concurrency.py	fastmanifest: fix some check code errors	2016-10-21 11:02:11 -07:00
constants.py	fastmanifest: add documentation of constants	2016-06-08 14:28:14 -07:00
debug.py	[fastmanifest] add a uiproxy object that forwards requests to a real ui object	2016-07-05 16:32:05 -07:00
implementation.py	hybridmanifest: don't reuse node in match results	2016-12-02 14:37:28 -08:00
metrics.py	fastmanifest: fix logic error for debugmetrics and simplify test	2016-07-06 13:42:32 -07:00