diff options
| author | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-09-15 00:26:36 +0200 |
|---|---|---|
| committer | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-09-15 00:26:36 +0200 |
| commit | f12f3f1356e4e96d419d66d13c2e67b73a50346f (patch) | |
| tree | c3d83c41030b0fae8252cc18783c40fa9c8d0f9d /docs | |
| parent | 8a046c897e42e9459aa99377589c80c773601efc (diff) | |
| download | krino-f12f3f1356e4e96d419d66d13c2e67b73a50346f.tar.gz krino-f12f3f1356e4e96d419d66d13c2e67b73a50346f.zip | |
an earlier directory's applied results stay claimed for later ones
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/design.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/design.md b/docs/design.md index ca8d550..43a6975 100644 --- a/docs/design.md +++ b/docs/design.md @@ -475,7 +475,9 @@ finds a target another step of the same plan has already claimed, it takes the next free name instead, because that path will hold the other step's output by the time either runs, and displacing it would destroy that step's result. A real run applies each directory before planning the next, so a later -directory sees the earlier one's result on disk and its claims end with it. +directory sees the earlier one's result on disk; of its claims only the paths +it actually put files at carry over, so a later `overwrite` never displaces +this run's own result. A dry run (`-n`) applies nothing: its claim set spans every directory, so two configured directories cannot show the same final name, but each directory is otherwise planned as if no earlier one had been applied (a file the first |
