libpijul 0.12.2

A patch-based distributed version control system, easy to use and fast.
docs.rs failed to build libpijul-0.12.2
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: libpijul-1.0.0-beta.10
This crate contains the core API to access Pijul repositories. The key object is a `Repository`, on which `Txn` (immutable transactions) and `MutTxn` (mutable transactions) can be started, to perform a variety of operations. Another important object is a `Patch`, which encodes two different pieces of information: - Information about deleted and inserted lines between two versions of a file. - Information about file moves, additions and deletions. The standard layout of a repository is defined in module `fs_representation`, and mainly consists of a directory called `.pijul` at the root of the repository, containing: - a directory called `pristine`, containing a Sanakirja database storing most of the repository information. - a directory called `patches`, actually containing the patches, where each patch is a gzipped compression of the bincode encoding of the `patch::Patch` type. At the moment, users of this library, such as the Pijul command-line tool, may use other files in the `.pijul` directory, such as user preferences, or information about remote branches and repositories.