Say in to-be 47 that a stop's closed window cuts the batch's unrelated merges early (review of #232, issue 459)

2026-10-11 21:16:05 +02:00
parent f8efb08b3d
commit ce67b65c10
1 changed files with 3 additions and 2 deletions
@@ -181,8 +181,9 @@ delivery on it. A stop therefore ends only the change it is for:
  walked again.
 - **Where the others go.** They join the open batch of their kind, where merges heard while the walk ran
  already wait, so an older commit never walks after a newer one; only with none open do they form a new
-  batch. The stop closes that batch's window, and its walk withholds the left-out merges' modules where it
-  would build them only as dependents. A batch not yet cut can be stopped without a merge too: the merge goes
+  batch. The stop closes that batch's window, so the unrelated merges in it, and any heard after the stop
+  before it is cut, are cut without the rest of their window. Its walk withholds the left-out merges' modules
+  where it would build them only as dependents, and its record names them. A batch not yet cut can be stopped without a merge too: the merge goes
  to a stopped record of its own, and the batch goes on without it. The stopped record, the batch and every
  merge moved are written in one transaction.
 - **The walk's record.** The stopped walk names the batch that walks its merges again, every merge it left