diff options
| author | Joey Hess <joeyh@joeyh.name> | 2024-01-25 13:10:45 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2024-01-25 13:10:45 -0400 |
| commit | 7aee4ca7c17d1a47f5aabc44b14b88c99a0db819 (patch) | |
| tree | 978e2cf25f2fbe3dcdbeff301ac9c21d3b6daf02 | |
| parent | 8646183e3833427f5a450d831008b8297292a244 (diff) | |
nack
| -rw-r--r-- | doc/todo/worktree_overwrite_races.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/todo/worktree_overwrite_races.mdwn b/doc/todo/worktree_overwrite_races.mdwn index 815e438a7d..d11bb3c7e8 100644 --- a/doc/todo/worktree_overwrite_races.mdwn +++ b/doc/todo/worktree_overwrite_races.mdwn @@ -32,3 +32,14 @@ place. It gets 3 appended to it. So the worktree file ends up containing `1,3`. So, perhaps there is really no good solution to this. --[[Joey]] + +> I suppose the balance of probabilities is that a worktree file being +> overwritten in the current race window is fairly plausibly likely, +> while a file being repeatedly appended to in that way is very unlikely. +> +> But the balance of ill effects is that in the current case you lose data +> in a way that is easy to understand (and that git is also subject to), +> and in the repeated append case, a file gets into a state it never ought +> to possibly be in. +> +> So I think it makes sense to abandon this idea. [[done]] --[[Joey]] |