Overview
| Comment: | zit init --submanifest K starts a repository with sub-manifests on and k pinned, so a tree that will grow wide is a tree from its first check-in |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
1fbc90c725abd52a6454c8ac79e0bcef |
| User & Date: | dmestas on 2026-11-04 15:52:58.534 |
| Other Links: | manifest | tags |
Context
|
2026-11-04
| ||
| 16:01 | The horizon draft says a tied candidate that another descends from through any parent is dropped, merge parents included check-in: b09ee3ed91 user: dmestas tags: trunk | |
| 15:52 | zit init --submanifest K starts a repository with sub-manifests on and k pinned, so a tree that will grow wide is a tree from its first check-in check-in: 1fbc90c725 user: dmestas tags: trunk | |
| 14:29 | File reads and writes move at most 1 GiB per call, so on macOS a store whose cache passes 2 GiB resumes from it instead of re-deriving the whole history check-in: 3d4b8d295c user: dmestas tags: trunk | |
Changes
Modified src/cli.zig
from [e729a555ca]
to [6f7f0aebed].
[diff]
Modified src/e2e.zig
from [762ece4e31]
to [4b33d284f5].
[diff]
Modified src/main.zig
from [be78110fd8]
to [04b13e0383].
[diff]
Modified www/reference.html
from [102bd1bcef]
to [f79d5fb6ce].
[diff]