diff options
| author |  Richard Hartmann <richih@debian.org> | 2015-10-12 22:50:16 +0200 |
|---|---|---|
| committer | Richard Hartmann <richih@debian.org> | 2015-10-12 22:50:16 +0200 |
| commit | 8a7e76e9b03ca22ac0c44852974dcedf90d37787 (patch) | |
| tree | ad13514598b4317bf080163949503bc910365075 /doc/devblog/day_322-326__concurrent_drop_safety.mdwn | |
| parent | 5e14a953193f16d53c4ce59c714a587927b88a03 (diff) | |
doc/devblog/day_322-326__concurrent_drop_safety.mdwn: Wording
Diffstat (limited to 'doc/devblog/day_322-326__concurrent_drop_safety.mdwn')
| -rw-r--r-- | doc/devblog/day_322-326__concurrent_drop_safety.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/devblog/day_322-326__concurrent_drop_safety.mdwn b/doc/devblog/day_322-326__concurrent_drop_safety.mdwn index 6b8da87f7..5dbf420e4 100644 --- a/doc/devblog/day_322-326__concurrent_drop_safety.mdwn +++ b/doc/devblog/day_322-326__concurrent_drop_safety.mdwn @@ -41,9 +41,9 @@ rare race condition occurs. So, I've been implementing that all of yesterday and today. Getting it right involves building up 4 different kinds of evidence, which can be -used to make sure that the last copy of a file can't possibly be being +used to make sure that the last copy of a file can't possibly end up being dropped, no matter what other concurrent drops could be happening. I ended up with a very clean and robust implementation of this, and -a 2 thousand line diff. +a 2,000 line diff. Whew! |