mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 00:45:18 +03:00
eef0c650e7
Summary: Previously the mutation commit extras were the source of truth for mutation information, and the mutation store served as a kind of cache. This turned out to be less useful than expected, as oftentimes commits are missing, and the store is better indexed, so in practice using the store as the source of truth is better. This change makes the mutationstore the (sole) source of truth for mutation data. The extras are kept, but they are now only useful as human-readable debug information, and to ensure the commit hash is unique. Collecting the mutation information during commit creation is now done through a new `mutinfo` object. This is a dict with the same keys as the mutation extras, for simplicity, but it is now passed through the `committablectx` and used to generate the mutation store entry directly. The `mutation.enabled` config option is now used to control all aspects of enabling mutation. The `mutation.record` config option is now only used to indicate whether the mutation extras should also added to the commit. Generally this should be set to `true`, however the option is retained so that mutation extras can be stripped by running `hg amend --config mutation.record=false`, which no longer has the side-effect of not recording mutation information to the store. The "remote commit" mutation record origin is now obsolete, and won't be generated anymore. Pushrebase now relies on the obsmarker information coming back from the server in order to correctly generate mutation information. We will need to change this so that the server returns mutation records before we can fully deprecate obsmarkers. Reviewed By: DurhamG Differential Revision: D19410650 fbshipit-source-id: 8d7094e4bfd8d8e97916898d899a8debd339485f |
||
|---|---|---|
| .. | ||
| hgdemandimport | ||
| hgext | ||
| mercurial | ||
| __init__.py | ||
| traceimport.py | ||