3966192f01
Summary: The main reason for doing it is to remove dependency on `BlobRepo` from hooks. Most of the `hooks` crate code needs from `BlobRepo` just a HgBlobChangeset type, which was moved to a separate crate in one of the previous diffs. There is just a small piece of code that depends on blobrepo, and it was moved in the separate crate. Because of that changing anything in BlobRepo won't trigger rebuilding of most of the hooks crate. Reviewed By: lukaspiatkowski Differential Revision: D13878208 fbshipit-source-id: d74336e959282c176258c653d4c408854e1f1849 |
||
|---|---|---|
| apiserver | ||
| async-compression | ||
| asyncmemo | ||
| blobimport_lib/src | ||
| blobrepo | ||
| blobrepo_utils | ||
| blobstore | ||
| blobstore-sync-queue | ||
| bonsai-hg-mapping | ||
| bonsai-utils | ||
| bookmarks | ||
| bundle2-resolver | ||
| bytes-ext | ||
| cache-warmup/src | ||
| changesets | ||
| cmdlib/src | ||
| cmds | ||
| common | ||
| failure_ext | ||
| filenodes | ||
| futures-ext | ||
| hgcli | ||
| hgproto | ||
| hook_tailer | ||
| hooks | ||
| mercurial | ||
| mercurial-bundles | ||
| mercurial-types | ||
| metaconfig | ||
| mononoke-api/src | ||
| mononoke-types | ||
| netstring/src | ||
| phases | ||
| py_tar_utils | ||
| reachabilityindex | ||
| ready_state/src | ||
| repo_client | ||
| revset | ||
| server | ||
| sshrelay | ||
| tests | ||
| .gitignore | ||
| .travis.yml | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| packman.yml | ||
| README.md | ||
| rustfmt.toml | ||
Mononoke
Mononoke is a next-generation server for the Mercurial source control system, meant to scale up to accepting thousands of commits every hour across millions of files. It is primarily written in the Rust programming language.
Caveat Emptor
Mononoke is still in early stages of development. We are making it available now because we plan to start making references to it from our other open source projects such as Eden.
The version that we provide on GitHub does not build yet.
This is because the code is exported verbatim from an internal repository at Facebook, and not all of the scaffolding from our internal repository can be easily extracted. The key areas where we need to shore things up are:
- Full support for a standard
cargo build. - Open source replacements for Facebook-internal services (blob store, logging etc).
The current goal is to get Mononoke working on Linux. Other Unix-like OSes may be supported in the future.