mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 17:27:53 +03:00
8a79cfa7e8
Summary: If some bundle consisted of several snapshots, and the client requests a part of that data, the server can trigger the rebundling process. This diff teaches snapshots to the rebundling process. The `bundlerepo` object should store data in memory, so a `unionstore` class is made up. It allows to "pair" in-memory store with a regular local store and query them via the same API. Reviewed By: markbt Differential Revision: D17684945 fbshipit-source-id: 0bdb1f70b777fb2d8193b3bfa46b5915c2019663 |
||
---|---|---|
.. | ||
__init__.py | ||
bookmarks.py | ||
bundleparts.py | ||
bundlestore.py | ||
client.py | ||
common.py | ||
constants.py | ||
fileindex.py | ||
infinitepushcommands.py | ||
README | ||
server.py | ||
sqlindex.py |
## What is it? This extension adds ability to save certain pushes to a remote blob store as bundles and to serve commits from remote blob store. The revisions are stored on disk or in everstore. The metadata are stored in sql or on disk. ## Config options infinitepush.branchpattern: pattern to detect a scratchbranch, example 're:scratch/.+' infinitepush.indextype: disk or sql for the metadata infinitepush.reponame: only relevant for sql metadata backend, reponame to put in sql infinitepush.indexpath: only relevant for ondisk metadata backend, the path to store the index on disk. If not set will be under .hg in a folder named filebundlestore infinitepush.storepath: only relevant for ondisk metadata backend, the path to store the bundles. If not set, it will be .hg/filebundlestore