This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

2026-10-31 — spc-2609202134338445 step 11, fix round 3: the auto-plan's checkout digest folds in, for the checkout's index, the SHA-256 of the copy's entries as git ls-files -z --stage -t -v lists them, next to the tree write-tree makes of the copy, and both run on the copy with core.splitIndex off. Grounds: write-tree leaves intent-to-add entries out of the tree and records no entry flags, so an intent-to-add entry or a skip-worktree flag changed the person's index with HEAD, the tree and the working tree unchanged; the listing carries each entry's mode, object, stage, path and flag tags but no cached file stats, so a stat refresh still changes nothing; -z keeps every path unambiguous. With core.splitIndex on, git writes a new shared index file into the git directory when it writes a copy, so every scratch index the shared helper runs on is written whole, inside the scratch directory.

decisiondcn-2610311310334354

2026-10-31 — spc-2609202134338445 step 11, fix round 3: the auto-plan's checkout digest folds in, for the checkout's index, the SHA-256 of the copy's entries as git ls-files -z --stage -t -v lists them, next to the tree write-tree makes of the copy, and both run on the copy with core.splitIndex off. Grounds: write-tree leaves intent-to-add entries out of the tree and records no entry flags, so an intent-to-add entry or a skip-worktree flag changed the person's index with HEAD, the tree and the working tree unchanged; the listing carries each entry's mode, object, stage, path and flag tags but no cached file stats, so a stat refresh still changes nothing; -z keeps every path unambiguous. With core.splitIndex on, git writes a new shared index file into the git directory when it writes a copy, so every scratch index the shared helper runs on is written whole, inside the scratch directory.

Frontmatter

iddcn-2610311310334354
typedecision
date2026-10-31

mentions1