From 7d3eb6d47dc65824a8e41958d05898809b336b29 Mon Sep 17 00:00:00 2001 From: spwhitton Date: Mon, 21 Sep 2015 21:22:22 +0000 Subject: [PATCH] Added a comment --- .../comment_2_a6c8200184dab2ff3658843d412e5e1b._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down/comment_2_a6c8200184dab2ff3658843d412e5e1b._comment diff --git a/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down/comment_2_a6c8200184dab2ff3658843d412e5e1b._comment b/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down/comment_2_a6c8200184dab2ff3658843d412e5e1b._comment new file mode 100644 index 0000000000..f2d7196ef2 --- /dev/null +++ b/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down/comment_2_a6c8200184dab2ff3658843d412e5e1b._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="spwhitton" + subject="comment 2" + date="2015-09-21T21:22:22Z" + content=""" +I am not aware of any problems other than the noise, but I think it's significant noise because it's marked with 'WARNING' in block capitals and this makes the user worry that something might have gone wrong with their precious git-annex data, and there's no indication it can be automatically recovered from. + +Would you accept a patch to your fork of git-remote-gcrypt, since the original author is inactive? +"""]]