aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down/comment_2_a6c8200184dab2ff3658843d412e5e1b._comment
blob: f2d7196ef216b1dbfc79f591fd900608c61e705c (plain)
1
2
3
4
5
6
7
8
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?
"""]]