| Comment: | grep: read manifests only where the record says PATH changed (zit#178)
One record scan, as annotate, instead of a manifest per check-in: 20,937 reads to 272 on VERSION, 19s to 0.4s. Each version is reported once under its oldest introducer, matching fossil grep's list byte for byte. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
6be0341149431a86bd7253e59f202785 |
| User & Date: | dmestas on 2026-09-06 20:06:37.019 |
| Other Links: | manifest | tags |
|
2026-09-06
| ||
| 20:47 |
timeline: read the image, not a full derive (zit#181)
The image has carried adjacency since layout 2 and comment/login since layout 6, so every default row renders from the zero-parse path; only full/-v/-p still read manifests. 60 ms to 8 ms on a 22k check-in store, output byte-identical across formats. check-in: 18ffce5678 user: dmestas tags: trunk | |
| 20:06 |
grep: read manifests only where the record says PATH changed (zit#178)
One record scan, as annotate, instead of a manifest per check-in: 20,937 reads to 272 on VERSION, 19s to 0.4s. Each version is reported once under its oldest introducer, matching fossil grep's list byte for byte. check-in: 6be0341149 user: dmestas tags: trunk | |
| 14:06 |
sync: read the Content-Type media type, not the whole header (zit#179)
A front web server that appends "; charset=utf-8" made the clone reply look compressed, so its plaintext was read as a 1.6 GB container and refused as too large. parseMediaType now ignores parameters and case, as fossil does; serve uses it instead of its own copy. check-in: 8488af309e user: dmestas tags: trunk, version-0.3.6 | |