mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 01:39:21 +03:00
161a6ddc0d
Summary: infinitepush rebundling wasn't passing the appropriate bundlecaps. This caused treeonly repositories to receive flat manifests from infinitepush bundles. This allowed treeonly clients to receive the data and convert it to trees, but really we should just convert the data to trees on the server before we send and not rely on the client to be able to accept flat manifests. Now that we no longer send flat manifests, we rely on the recently added conversion logic to turn flat manifests into trees when necessary. This will be required for turning the server into a treeonly client anyway. Differential Revision: D7256556 fbshipit-source-id: bbaf9d4570eebd9f200004e34044b5b1a8c53e2e |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| backupcommands.py | ||
| bundleparts.py | ||
| common.py | ||
| fileindexapi.py | ||
| indexapi.py | ||
| infinitepushcommands.py | ||
| README | ||
| sqlindexapi.py | ||
| store.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