Skip to content
zit Check-in [6677853a3d]
Login

Check-in [6677853a3d]

Overview
Comment:settings: hazard-tiered model with a global tier and provenance (#83)
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 6677853a3da865acf6017fe14b0411f6e330386037b07de75e4ac3b44928796f
User & Date: dmestas on 2026-08-16 18:04:49.694
Other Links: manifest | tags
Context
2026-08-16
18:45
merge empty-trailing-token: C and J accept an empty trailing token (#86) check-in: b4893b3fee user: dmestas tags: trunk
18:04
settings: hazard-tiered model with a global tier and provenance (#83) check-in: 6677853a3d user: dmestas tags: trunk
17:44
smoke S9: require the carried shun row, not a phantom (#73)

Carrying the /shun config group means a fossil clone records the artifact as suppressed instead of holding a phantom for it. That is the better end state: a phantom is something fossil goes looking for, so the next sync with any third party would undo the takedown.

S9 asked for the phantom specifically and so went red. It now asks fossil's own shun table and REQUIRES the row — tolerating the phantom would leave the scenario unable to notice the carriage regressing. The phantom probe stays as a diagnostic that tells a lost row apart from a served artifact. check-in: 7c656e4718 user: dmestas tags: trunk

Changes