From 64639ff9b19e50ff1f25e91c378e9e4b5178c522 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 26 Feb 2020 18:29:06 -0400 Subject: [PATCH] followup and close --- doc/bugs/gcrypt_special_remote_not_working.mdwn | 1 + doc/todo/network_test_suite.mdwn | 3 +++ 2 files changed, 4 insertions(+) diff --git a/doc/bugs/gcrypt_special_remote_not_working.mdwn b/doc/bugs/gcrypt_special_remote_not_working.mdwn index f6250645ca..c7850e76d3 100644 --- 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 eea7df952f..fafde3dcbb 100644 --- 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; -- 2.30.2