|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
|
# zit
Fossil, reimplemented from its specifications, in Zig.
zit is a clean-room implementation of the Fossil version-control formats
and sync protocol. The deliverable is a reusable library — a Zig
counterpart to libfossil — with the `zit` command as a thin consumer.
Nothing is ported from C: every rule, byte layout, and rejection
condition is taken from four Internet-Drafts frozen in this repository,
and every test cites the clause it covers.
## The specifications
The drafts under [docs/rfcs](dir?ci=trunk&name=docs/rfcs) are the sole
authority. Expected values in tests come from the spec text and its
worked examples, never from observing another implementation.
| Layer | Draft | Specifies |
|-------|-------|-----------|
| `delta` | [draft-fossil-delta-format-00](doc/trunk/docs/rfcs/draft-fossil-delta-format-00.txt) | byte-level delta encoding: copy/literal segments, base-64 integers, mod-2³² checksum |
| `artifact` | [draft-fossil-artifact-format-00](doc/trunk/docs/rfcs/draft-fossil-artifact-format-00.txt) | card-structured manifests and control artifacts, content addressing (SHA-1 / SHA3-256), checksums |
| `repostate` | [draft-fossil-repo-state-00](doc/trunk/docs/rfcs/draft-fossil-repo-state-00.txt) | branch, tag, and leaf state derived from the append-only artifact set |
| `sync` | [draft-fossil-sync-protocol-00](doc/trunk/docs/rfcs/draft-fossil-sync-protocol-00.txt) | HTTP replication of the artifact set between repositories |
Each layer depends only on the layers before it:
delta -> artifact -> repostate -> sync
That ordering is also the implementation order, and [src](dir?ci=trunk&name=src)
mirrors it module for module.
## Scope
zit implements the version-control substrate: check-in manifests,
clusters, and tag/control artifacts are parsed and interpreted. The
collaboration artifact types — wiki, ticket, forum, attachment,
technote — are carried opaquely: stored, named, and synchronized by
hash, never interpreted.
## Building
Requires Zig 0.16 or later.
zig build # produce zig-out/bin/zit
zig build run -- version
zig build test # unit tests, one cited test per RFC clause
## Finding your way
* [Timeline](timeline) — current activity and history
* [Source tree](dir?ci=trunk) — browse the code at trunk
* [README](doc/trunk/README.md) — checkout and build notes
* [docs/rfcs](dir?ci=trunk&name=docs/rfcs) — the four frozen drafts
|