| Comment: | erratum: sync §5.2 spells the bad-command text as bare words
The ABNF and §10.1 already make every error card one fossilized TEXT; the unknown-operator prose writes "error bad command: LINE" and reads as four tokens. Records the wire form and the two-token client rule. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
ec7d3fc9f7710caa5be026c1599fd7b6 |
| User & Date: | dmestas on 2026-09-17 16:27:05.311 |
| Other Links: | manifest | tags |
|
2026-09-17
| ||
| 17:04 |
Remove issue-tracker numbers from source and documents
The tracker is disposable and does not live with the source, so a number is a dangling pointer. Every zit#NN and #NN reference in code comments, test names, help text, smoke labels, identifiers, release notes and errata is replaced by enough context to stand alone, or by a short plain statement of the problem. No behaviour changed. check-in: 9033c13f21 user: dmestas tags: trunk | |
| 16:27 |
erratum: sync §5.2 spells the bad-command text as bare words
The ABNF and §10.1 already make every error card one fossilized TEXT; the unknown-operator prose writes "error bad command: LINE" and reads as four tokens. Records the wire form and the two-token client rule. check-in: ec7d3fc9f7 user: dmestas tags: trunk | |
| 15:29 | cli: format the remote URL check check-in: ae396d9bac user: dmestas tags: trunk, version-0.3.20 | |