| Comment: | merge quarry-support: ls --long and log --long (#96, #93) |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
15fa309b01daa1411411add967d2c04f |
| User & Date: | dmestas on 2026-08-17 13:33:19.267 |
| Other Links: | manifest | tags |
|
2026-08-17
| ||
| 14:29 |
Merge tag-list release filtering to trunk
Plain tag listing now reflects only singleton symbolic release names, while raw listing preserves complete repository tag state. Refs ticket a679b1197b61127930f7e2a6478145c561dd54cc. check-in: 24356ebb90 user: dmestas tags: trunk | |
| 13:58 | Create new branch named "fix-tag-list-release-filter" check-in: cf62ee5ea1 user: dmestas tags: fix-tag-list-release-filter | |
| 13:33 | merge quarry-support: ls --long and log --long (#96, #93) check-in: 15fa309b01 user: dmestas tags: trunk | |
| 13:27 |
ls --long and log --long: one invocation answers a page (#96, #93)
ls --long adds size, the F card's permission token, and text/binary. The permission is the fact no other verb can supply -- it lives in the manifest, and the blob it names does not know it is executable -- so a listing could not mark executables and mis-rendered symlinks. --under bounds the listing to one directory, which is also what makes --long's per-file content read affordable. log --long adds each check-in's timestamp, user and comment. log CHECKIN PATH already selected the check-ins touching PATH; emitting only hashes meant a file-history page cost a subprocess per row. Both are opt-in; the default outputs are byte-identical. A blob the store cannot produce reports 'absent' rather than a zero-byte text file. closed check-in: f01eb5b6a0 user: dmestas tags: quarry-support | |
| 11:06 | merge sparse-cone: classify paths against the cone and name the deciding member (#79) check-in: 187ad81e8c user: dmestas tags: trunk | |