Artifact 1fcb1586b93465412f06965dc908e3881fd6a399305b1f5abf3d239568fdb910:
- File
docs/rfcs/erratum/artifact-format-00-s4.2-empty-trailing-token.md
-
2026-08-16 18:30:58
— part of check-in
[5ccb138e6d]
on branch empty-trailing-token
— C and J accept an empty trailing token (#86)
Fossil distinguishes an absent token from an empty one positionally: `C` LF has none and is rejected, `C` SP LF has one empty token and is a present, empty comment. zit implemented §4.2's `token = 1*tchar` literally and rejected the empty form on C and J, which drops the whole artifact — every ticket change with an empty field, every check-in with an empty comment. T and U were already right.
Two tests asserted the old behaviour and now assert the corrected one; a third pins the writer, since --submanifest re-mints every manifest. The RFC text is unchanged; docs/rfcs/erratum/ carries the correction. (user: dmestas, size: 8775) [annotate] [blame] [check-ins using]
- 2026-08-16 18:45:54 — part of check-in [b4893b3fee] on branch trunk — merge empty-trailing-token: C and J accept an empty trailing token (#86) (user: dmestas, size: 8775) [annotate] [blame] [check-ins using]
-
2026-08-16 18:30:58
— part of check-in
[5ccb138e6d]
on branch empty-trailing-token
— C and J accept an empty trailing token (#86)