diff options
| author |  Øyvind A. Holm <sunny@sunbase.org> | 2015-10-05 01:33:12 +0200 |
|---|---|---|
| committer | Øyvind A. Holm <sunny@sunbase.org> | 2015-10-05 01:33:12 +0200 |
| commit | cfd21d4a6a07e12a109a128c4d4f5e0b1d4bac08 (patch) | |
| tree | ead1415946e00d87b68b2552f3918bd7aece91c0 | |
| parent | e28da97a365b54555178c4d67d2414b58137e91d (diff) | |
Minor grammar fix in my comment
| -rw-r--r-- | doc/devblog/day_321__download_verification/comment_4_fecb2d6349aa61f1c76525178fea4598._comment | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/devblog/day_321__download_verification/comment_4_fecb2d6349aa61f1c76525178fea4598._comment b/doc/devblog/day_321__download_verification/comment_4_fecb2d6349aa61f1c76525178fea4598._comment index 6dc5d3e77..26d60c868 100644 --- a/doc/devblog/day_321__download_verification/comment_4_fecb2d6349aa61f1c76525178fea4598._comment +++ b/doc/devblog/day_321__download_verification/comment_4_fecb2d6349aa61f1c76525178fea4598._comment @@ -3,5 +3,5 @@ subject="Yay, man!" date="2015-10-04T23:28:43Z" content=""" -I love this! Especially since I've noticed some read errors on my laptop disk now and then. Not when using git-annex, I've never lost a file with it, but when doing other things. I've been hoping for this, as I've used computers with memory corruption years ago, and in cases like that, all bets are off and you'll only hope that the file copy goes well. I've grown quite paranoid after that computer, and have enabled everything in git (setting `fetch.fsckObjects`, `receive.fsckObjects` and `transfer.fsckObjects` to `true`) to catch potential errors as a result of bad disk, memory corruption or transfer errors over the network. I'd rather wait a bit longer while copying or especially moving files than waiting for that single corrupted bit in the only copy of a 4 gig file. Thanks! +I love this! Especially since I've noticed some read errors on my laptop disk now and then. Not when using git-annex, I've never lost a file with it, but when doing other things. I've been hoping for this, as I've used computers with memory corruption years ago, and in cases like that, all bets are off and you'll only hope that the file copy goes well. I've grown quite paranoid after that computer, and have enabled everything in git (setting `fetch.fsckObjects`, `receive.fsckObjects` and `transfer.fsckObjects` to `true`) to catch potential errors as a result of bad disk, memory corruption or transfer errors over the network. I'd rather wait a bit longer while copying or especially moving files than wait for that single corrupted bit in the only copy of a 4 gig file. Thanks! """]] |