From c6e4dcca673841f29449c8c2bf85fa41b31da12f Mon Sep 17 00:00:00 2001 From: Edward Betts Date: Sat, 11 Feb 2017 09:38:49 +0000 Subject: correct spelling mistakes --- .../comment_1_3e48e930616917f6db1fc351d0f7e6df._comment | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment') diff --git a/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment b/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment index f345e64b7..9c20baad7 100644 --- a/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment +++ b/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment @@ -4,7 +4,7 @@ subject="comment 1" date="2016-04-29T10:26:22Z" content=""" -> A bug made encrypted special remotes that are configured to use chunks accidentially expose the checksums of content that is uploaded to the remote. Such information is supposed to be hidden from the remote's view by the encryption. +> A bug made encrypted special remotes that are configured to use chunks accidentally expose the checksums of content that is uploaded to the remote. Such information is supposed to be hidden from the remote's view by the encryption. What should the users do to repair this situation? How can the exposed checksums be removed from the remote? Is a `git annex sync` enough? -- cgit v1.2.3