mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 01:07:15 +03:00
e57b1f9265
Summary: The Segmented Changelog must be built somewhere. One of the simplest deployments of involves the on-demand update of the graph. When a commit that wasn't yet processed is encountered, we sent it to processing along with all of it's ancestors. At this time not much attention was paid to the distinction of master commit versus non-master commit. For now the expectation is that only commits from master will exercise this code path. The current expectation is that clients will only call location-to-hash using commits from master. Let me know if there is an easy way to check if a commit is part of master. Later changes will invest more in handling non-master commits. Reviewed By: aslpavel Differential Revision: D23456218 fbshipit-source-id: 28c70f589cdd13d08b83928c1968372b758c81ad |
||
|---|---|---|
| .. | ||
| schemas | ||
| src | ||
| Cargo.toml | ||