23fe5a7780
Summary: The `reset` extension does its own obsmarker creation, rather than going through `scmutil.cleanupnodes`. This means it doesn't support new-style visibility tracking. Fix this by making it use `scmutil.cleanupnodes`. This isn't completely straightforward: * The revset it uses to work out what to prune might accidentally include public commits (e.g. when you reset to a different public branch). Make sure these are filtered. * The tests originally had strip and obsmarker based tests. The strip tests, when converted to obsmarkers and using `scmutil.cleanupnodes` stop working because they strip and revive the same commit over and over, which is an edge case that obsmarkers can't handle well. Fix this by restoring the strip tests as strip tests. A separate test handles the new-style visibility. * Reset's behaviour is still a bit wonky. If an ancestor of the source commit has other (non-bookmarked) descendants, then reset will try to prune those commits. New-style visibility will ignore this, and this is tested in the new test. Reviewed By: farnz Differential Revision: D18912817 fbshipit-source-id: cc115333407cf67d339c24fcd0807ddedce2660d |
||
---|---|---|
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.