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 |
||
|---|---|---|
| build | ||
| CMake | ||
| common | ||
| eden | ||
| .gitignore | ||
| .travis.yml | ||
| CMakeLists.txt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| getdeps.py | ||
| LICENSE | ||
| make-client.py | ||
| README.md | ||
EdenFS is a FUSE virtual filesystem for source control repositories.
EdenFS speeds up operations in large repositories by only populating working
directory files on demand, as they are accessed. This makes operations like
checkout much faster, in exchange for a small performance hit when first
accessing new files. This is quite beneficial in large repositories where
developers often only work with a small subset of the repository at a time.
EdenFS has similar performance advantages to using sparse checkouts, but a much better user experience. Unlike with sparse checkouts, EdenFS does not require manually curating the list of files to check out, and users can transparently access any file without needing to update the profile.
EdenFS also keeps track of which files have been modified, allowing very
efficient status queries that do not need to scan the working directory.
The filesystem monitoring tool Watchman
also integrates with EdenFS, allowing it to more efficiently track updates to
the filesystem.
Building EdenFS
EdenFS currently only builds on Linux. We have primarily tested building it on Ubuntu 18.04.
TL;DR
[eden]$ ./getdeps.py --system-deps
[eden]$ mkdir _build && cd _build
[eden/_build]$ cmake ..
[eden/_build]$ make
Dependencies
EdenFS depends on several other third-party projects. Some of these are commonly available as part of most Linux distributions, while others need to be downloaded and built from GitHub.
The getdeps.py script can be used to help download and build EdenFS's
dependencies.
Operating System Dependencies
Running getdeps.py with --system-deps will make it install third-party
dependencies available from your operating system's package management system.
Without this argument it assumes you already have correct OS dependencies
installed, and it only updates and builds dependencies that must be compiled
from source.
GitHub Dependencies
By default getdeps.py will check out third-party dependencies into the
eden/external/ directory, then build and install them into
eden/external/install/
If repositories for some of the dependencies are already present in
eden/external/ getdeps.py does not automatically fetch the latest upstream
changes from GitHub. You can explicitly run ./getdeps.py --update if you
want it to fetch the latest updates for each dependency and rebuild them from
scratch.
License
See LICENSE.