Skip to content
quarry Check-in [116d10e5cb]
Login

Check-in [116d10e5cb]

Overview
Comment:merge notes-first into trunk
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 116d10e5cb099097ddc068628af40e08d833061dc26b2254042b8214da75cfaf
User & Date: dmestas on 2026-08-24 09:46:33.651
Other Links: manifest | tags
Context
2026-08-24
09:52
landings: say the mimetype, and keep headings to one line

zit#136 shipped --mimetype, so a remark written in the composer is stored as the Markdown it previewed as. zit#138: the title card holds the whole -m message, so the heading takes its first line. check-in: 73367a3820 user: dmestas tags: trunk

09:51
about: the notes and announcement rows join the panel's icon grammar

Every other row in the About panel is icon + label, and .about-sub indents 1.5rem to clear that icon. These two had no icon, so their excerpt and date hung indented under nothing. A wrapping title also needs baseline alignment, or its later lines slide back under the icon.

The note now says who wrote it, as the feed does. check-in: d6a6146502 user: dmestas tags: trunk

09:46
merge notes-first into trunk check-in: 116d10e5cb user: dmestas tags: trunk
09:46
about: a project's news comes before its version list

Notes sat third in the sidebar, under Tags. What a project has been doing is a better first answer to "what is this" than which versions it has cut — and with no tab, this is a main door to them, which reads poorly third. closed check-in: d1dde173e0 user: dmestas tags: notes-first

09:41
landing page: probe the tip pair instead of scanning for the record

zit#134: landing show has to walk the whole store to FIND the record before it can answer about it, and quarry already folded that record out of its own index. zit merge --probe names the two check-ins, so the walk disappears -- 0.005s against 0.18s on this forge's own store, and the gap widens with store size, not with the number of landings.

Probing the same tips the cache is keyed on also closes a race: the key was built from resolved tips while the probe re-resolved a branch name, so a push landing between the two cached an answer under a key it did not describe.

An unresolvable tip now skips the probe instead of keying on ':' -- every landing whose branch could not be resolved shared that one cache entry and could be served another landing's verdict. check-in: bb05986ad8 user: dmestas tags: trunk

Changes