From 2911c6887c7fcda1d96ee4cb45d120344a428cb3 Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@joeyh.name>
Date: Mon, 2 Mar 2020 11:55:34 -0400
Subject: [PATCH] link

---
 .../comment_1_7eadb5e4cdebed6bffee5182b4bfe87b._comment        | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/bugs/gcrypt_special_remote_not_working/comment_1_7eadb5e4cdebed6bffee5182b4bfe87b._comment b/doc/bugs/gcrypt_special_remote_not_working/comment_1_7eadb5e4cdebed6bffee5182b4bfe87b._comment
index 90c0d166c6..2bd1879e07 100644
--- a/doc/bugs/gcrypt_special_remote_not_working/comment_1_7eadb5e4cdebed6bffee5182b4bfe87b._comment
+++ b/doc/bugs/gcrypt_special_remote_not_working/comment_1_7eadb5e4cdebed6bffee5182b4bfe87b._comment
@@ -3,8 +3,9 @@
  subject="""comment 1"""
  date="2020-02-26T19:04:47Z"
  content="""
-Almost certainly a reversion caused by the special
+Reversion caused by the special
 remote config overhaul in version 7.20200202.7.
+<https://git-annex.branchable.com/todo/assure_correct_names___40__and_values__41___for_special_remotes_parameters/>
 
 This is really bad. The one good thing is it does not
 seem to affect other types of special remotes, including