aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorLukasz Kasprzak <lukas@labunix.xyz>2026-09-15 00:41:00 +0200
committerLukasz Kasprzak <lukas@labunix.xyz>2026-09-15 00:41:00 +0200
commit2e812847572839e6c8097a7ecf5c4a469222087a (patch)
treef2c8908d235469dbdb4091984231d2ddb3beb3c8 /docs
parent2a7452c3fd83000f239755825f38246f8537b6cc (diff)
downloadkrino-2e812847572839e6c8097a7ecf5c4a469222087a.tar.gz
krino-2e812847572839e6c8097a7ecf5c4a469222087a.zip
only where an earlier directory's files ended up stays claimed
Diffstat (limited to 'docs')
-rw-r--r--docs/design.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/design.md b/docs/design.md
index e8dd1af..bda6b58 100644
--- a/docs/design.md
+++ b/docs/design.md
@@ -478,8 +478,8 @@ 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; of its claims only the paths
-it actually put files at carry over, so a later `overwrite` never displaces
-this run's own result.
+its files ended up at (each copy, and a moved or renamed file's last place)
+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