Durham Goode 311e30746f grep: handle sharded biggrep responses ... Summary: Biggrep recently moved to a sharded system where fbsource is spread over three shards and can have three different corpus revs. Let's update hg's biggrep integration to handle this new logic. We basically just take the earliest corpus commit and diff that against the users commit. There's room for some incorrectness here, like if the users commit is based off a commit before the earliest corpus commit then it will receive changes from the alter corpus commits. Long term biggrep will work on unifying the various shards to use a consistent corpus rev, but for now this is probably acceptable. Reviewed By: quark-zju Differential Revision: D23057055 fbshipit-source-id: 745cafe772cea44bbe2d8eb1eee70dd317f255fe		2020-08-13 09:58:52 -07:00
..
fs	add unique return code for unhealthy instance before restart	2020-08-13 09:44:11 -07:00
integration	add unique return code for unhealthy instance before restart	2020-08-13 09:44:11 -07:00
locale	add a copyright header to glibc_en.po	2019-04-26 14:38:27 -07:00
mononoke	mononoke: use VecDeque in blame_range_split_at	2020-08-13 08:32:41 -07:00
scm	grep: handle sharded biggrep responses	2020-08-13 09:58:52 -07:00
scripts	packaging: use scheduled tasks	2020-06-10 19:29:15 -07:00
test_support	Manually upgrading eden, and fixing their config	2020-08-06 12:37:04 -07:00
test-data	enable treemanifest in snapshots	2019-08-28 18:46:03 -07:00
.clang-format	Cut FOR_EACH_KV	2020-06-10 19:29:43 -07:00
.gitignore	eden: wire up mac contbuild	2019-02-05 21:52:30 -08:00
Eden.project.toml	Eden.project.toml file for Nuclide	2018-04-26 11:05:23 -07:00