| Comment: | search: the tree is searchable — documentation and source
quarry rendered both as first-class surfaces (the docs tab, the file browser) and could find neither. Fossil searches documentation but not source; this does both, from one pass. One tarball, not a read per file. cat per path costs a subprocess and a store open each: 2,199 files on sqlite is ~31s, against 2.2s for one archive — the tarball is the whole tree in one pass, which is the shape of the question. Tip-only. Indexing every revision of every file would dwarf the rest of the index many times over to answer a question nobody asks; what a file used to say is a question its own history answers. ref carries the version, not just the path: a link has to name the check-in the row was indexed at, and resolving a branch name at click time would be a second source of truth about which tree the row describes. Binaries and files over 1MB are skipped and counted — a search that silently covers less than the tree beside it is the failure this change is about. |
|---|---|
| Timelines: | family | ancestors | descendants | both | tree-search |
| Files: | files | file ages | folders |
| SHA3-256: |
8df971b482da325687b9928bc6427fba |
| User & Date: | dmestas on 2026-08-24 21:19:47.879 |
| Other Links: | branch diff | manifest | tags |
|
2026-08-24
| ||
| 21:19 | merge tree-search into trunk check-in: cd06e1345b user: dmestas tags: trunk | |
| 21:19 |
search: the tree is searchable — documentation and source
quarry rendered both as first-class surfaces (the docs tab, the file browser) and could find neither. Fossil searches documentation but not source; this does both, from one pass. One tarball, not a read per file. cat per path costs a subprocess and a store open each: 2,199 files on sqlite is ~31s, against 2.2s for one archive — the tarball is the whole tree in one pass, which is the shape of the question. Tip-only. Indexing every revision of every file would dwarf the rest of the index many times over to answer a question nobody asks; what a file used to say is a question its own history answers. ref carries the version, not just the path: a link has to name the check-in the row was indexed at, and resolving a branch name at click time would be a second source of truth about which tree the row describes. Binaries and files over 1MB are skipped and counted — a search that silently covers less than the tree beside it is the failure this change is about. closed check-in: 8df971b482 user: dmestas tags: tree-search | |
| 20:29 | merge doc-reindex into trunk check-in: 1631ff8ecc user: dmestas tags: trunk | |