Skip to content
zit Timeline
Login

Timeline

15 descendants of 399cc6b321edb49a

2026-11-06
18:17
zit daemon records merges: commit takes a parents list, written as zit merge and a commit write it, so two devices sending the same merge converge on one check-in; merge_base and diff ops answer read-only, diff sharing its comparison with zit diff leaf check-in: 4aab5d6849 user: dmestas tags: trunk
16:55
The release workflow checks the version constant in main.zig, where the version string now lives check-in: 9423667c03 user: dmestas tags: trunk
16:13
Release 0.10.0 check-in: 9fd9d8e3e9 user: dmestas tags: trunk, version-0.10.0
15:47
zit daemon answers lookup: whether a check-in with a given time, user and comment is stored, optionally on a given parent, by the same match a resend uses, without taking the writer lock or writing check-in: abb6786b0e user: dmestas tags: trunk
14:30
A commit may rename a file and give it new content in one check-in, as a rename plus a put of its new name; commit takes --date-override with Fossil's formats, and with -R a resend carrying the same date, user and comment answers with the stored check-in check-in: 560c41cefc user: dmestas tags: trunk
13:56
New names follow Fossil's strict path rule when written by commit, add, addremove and mv: valid UTF-8, nothing above U+FFFF, no private-use characters, no backslash, plus no control bytes; user and branch refuse control bytes; Fossil's reserved names are refused; names read from existing check-ins stay lenient, so a delete or rename can remove one check-in: d040bd2d7f user: dmestas tags: trunk
12:58
zit daemon serves one store over a local Unix socket: commit, batch with one fsync per batch, feed, get and status as JSON with raw trailers, acknowledging only after the fsync; a resend is matched on time, user and comment and answered with the stored check-in; the socket directory and file are owner-only and other users are refused check-in: d78ffcad0b user: dmestas tags: trunk
04:10
commit -R takes repeatable --rename OLD NEW and --delete PATH with or without --stdin, applied as one check-in through the direct-commit core, byte-identical to mv or rm and a checkout commit; a resend of a stored request returns its check-in check-in: 289dd7f6b7 user: dmestas tags: trunk
02:58
commit -R --stdin records through a direct-commit core that builds the check-in from the parent manifest and its edits, with no ephemeral checkout, byte-identical to a checkout commit of the same change; the core takes put, delete and rename, imports nothing from the CLI, and a caller holding it open commits in about 20 ms on a 42k-file tree store check-in: e1d2e2fbff user: dmestas tags: trunk
00:23
annotate --partial reads through a purged or shunned version and marks the lines it cannot trace with '~', exiting 0; plain annotate still refuses with exit 8 check-in: 3a52ad2bc9 user: dmestas tags: trunk
2026-11-05
22:54
Release 0.9.1 check-in: 7b62e60bb2 user: dmestas tags: trunk, version-0.9.1
22:50
log PATH -F json lists a purged, shunned or elided version with null size and its reason instead of failing; log PATH for a name no check-in held answers from the file index without walking history; a clone that fails before its store commits removes what it made; help exit-codes lists commit's exit 3 check-in: a22983364f user: dmestas tags: trunk
21:24
Smoke starts every fossil and zit server through the retrying starter, so a port taken between pick and bind tries a fresh one, and a server that never binds is reported with how it ended and its stderr check-in: affdc72275 user: dmestas tags: trunk
19:13
Release 0.9.0 check-in: b4566e6aad user: dmestas tags: trunk, version-0.9.0
18:43
purge artifacts removes named file versions to thin a history, keeping every check-in and refusing any version an open leaf or the checkout holds; a local .zit-thinned list keeps pull and serve from bringing them back; cat, diff and annotate exit 8 for content absent by policy, and annotate no longer credits a removed version's lines to the next one check-in: 79903b742d user: dmestas tags: trunk
15:54
crosslink --lines finds each changed file's old side by name, through the parent's sub-manifest slots or a search of its F cards, instead of flattening the parent's whole tree per check-in, and reads parent manifests through its plaintext cache check-in: 399cc6b321 user: dmestas tags: trunk