mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 17:58:27 +03:00
4578cd921f
Summary: When calculating bundleroots (the commits that are the common ancestors for the infinitepush bundle), we currently include all the `nullid` parents (i.e. p2 for most commits). This bloats the size of the list, and is unnecessary. Reviewed By: quark-zju Differential Revision: D14385912 fbshipit-source-id: c518b8b1aa27cff8562c2358a024b8a08ced8cba |
||
|---|---|---|
| .. | ||
| __init__.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