aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down.mdwn')
-rw-r--r--doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down.mdwn b/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down.mdwn
index 35e5111b6..332748123 100644
--- a/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down.mdwn
+++ b/doc/bugs/gcrypt_gives_false___34__remote_ID_has_changed__34___warning_after_a_sync_fails_because_network_is_down.mdwn
@@ -41,3 +41,5 @@ My diagnosis is that when running `git annex sync testremote --content` when the
(non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote's git config)
failed
+
+> fowarded, so [[closing|done]] --[[Joey]]