Concepts

How a Fossil repository is put together, and how go-libfossil implements it. Each page names the Internet-Draft in conformance/rfcs/ that specifies the behaviour.

• Architecture: packages, drivers, observers and the simulator.
• Artifacts: the text manifests that make up history, and how they are named.
• Repository state: the tables derived from the artifacts.
• Sync: the card protocol that clones, pulls and pushes.
• Sub-manifests: check-ins written as trees instead of flat file lists.
• Sparse cones: holding part of a repository by path.
• Horizons: holding part of a repository by age.
• Signing: clear-signed check-ins and signed horizon seeds.