From 2025673216395b8522b21f3fc31873e1f8515e31 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 23:37:48 +0100 Subject: [PATCH] Design 47 H: H-A-214, a take-in again covers the trunk; pipeline-wanted names the revision --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index ef5c0876..65fdcd95 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -1174,3 +1174,10 @@ Where two preparers disagreed, the chosen one is named. source) and, on a catalog-revision event, reads that revision by number through the revision verb, never the newest half; "waits for revision" compares numbers. Every revision a pipeline runs on is pinned (H-A-147, S33), a release revision too. P1, P4, P7. +- **H-A-214 (a take-in again covers the trunk; pipeline-wanted names the revision, 23:37)** Met in the build of H-A-212: + the taken state keeps only the trunk's merge commit, so a take-in again re-reads the trunk alone; another watched + branch is re-read at its next merge (its own take-in), which is enough for a branch that lives shortly (P3). The seat + mesh-wants' pipeline-wanted event names the pipeline's revision number beside its source, so the indexer frees the + pins of that revision and not of another revision of the same source; where the field is absent the indexer takes + the lowest-numbered revision of the source (the take-in's). The call's kind is one of three constants: take-in, + release, take-in-again. P1, P7.