followup and close

diff --git a/doc/bugs/gcrypt_special_remote_not_working.mdwn b/doc/bugs/gcrypt_special_remote_not_working.mdwn
index f6250645cac6f70871cfcc6e3a88c74649379c91..c7850e76d34d9b3c0c61d1f7bc8194524e836ba5 100644 (file)
--- a/doc/bugs/gcrypt_special_remote_not_working.mdwn
+++ b/doc/bugs/gcrypt_special_remote_not_working.mdwn
@@ -48,3 +48,4 @@ remote annex size: 10 bytes
 
 I am using git-annex since 2014 for all kinds of situations and I am very grateful for all the work you've put into this software. It even gets better over time ;)
 
+> [[fixed|done]] in git-annex 7.20200226. --[[Joey]]

diff --git a/doc/todo/network_test_suite.mdwn b/doc/todo/network_test_suite.mdwn
index eea7df952f544640226e697a99c50a3af0bcb3a9..fafde3dcbb0643cf397db87e093f863010739b71 100644 (file)
--- a/doc/todo/network_test_suite.mdwn
+++ b/doc/todo/network_test_suite.mdwn
@@ -20,6 +20,9 @@ More examples:
   could at least try to multicast back to the same host)
 * git-annex addurl and git-annex importfeed with http urls.
   And testing the various security configs that affect them.
+* The reversions where git-annex forgot to encrypt content stored
+  on gcrypt and git-lfs remotes could have been detected if there was a
+  test suite that tested them.
 
 This could be done as a new command or a flag to `git annex test`.
 In any case, the new test suite would need to be run somewhere;