| Comment: | Create new branch named "sparse-cone" |
|---|---|
| Timelines: | family | ancestors | descendants | both | sparse-cone |
| Files: | files | file ages | folders |
| SHA3-256: |
a620c242548a8e17cfd5630c68768bce |
| User & Date: | dmestas on 2026-08-17 00:14:30.853 |
| Other Links: | branch diff | manifest | tags |
|
2026-08-17
| ||
| 01:05 |
cone test: classify paths against the cone and name the deciding member (#79)
Longest match across both polarities decides coverage, so the verdict alone cannot say why a file is missing. The member prints bare so it pastes into zit cone remove. Exits 0 when every path is covered, 1 when any is elided. closed check-in: 3cb62134a3 user: dmestas tags: sparse-cone | |
| 00:14 | Create new branch named "sparse-cone" check-in: a620c24254 user: dmestas tags: sparse-cone | |
|
2026-08-16
| ||
| 21:47 |
binary-glob and crlf-glob: declarative content policy (#81)
Both are opt-in: an unset glob is no opinion, not refuse-everything, so a repository that never set one commits exactly as before. Set binary-glob to *.png and PNGs are the binaries the project expects, so a stray .o is refused. Neither runs code, so unlike before-commit they bind a fresh clone with no consent step -- that asymmetry is why they exist. The check gates what a commit INTRODUCES: an all-files commit re-captures every managed path, so classifying unchanged content would make declaring a glob block every later commit until the whole tree already conformed. Comparing against the parent's blob grandfathers inherited files, per content rather than per path, so editing one re-checks it. --no-checks waives it, the same flag that waives before-commit. check-in: 2711adbb03 user: dmestas tags: trunk | |