summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar pot <pot@web>2016-07-25 18:23:13 +0000
committerGravatar admin <admin@branchable.com>2016-07-25 18:23:13 +0000
commit0d35a61802aad5a70dfdf877dd72e1435b12aa98 (patch)
tree56caf11fe45be0c8edd8290378a09f2d1d1d177b /doc
parent4d7c4de31b8a8ff65b1680dd1d990fa6498bb2fa (diff)
Added a comment: Same issue
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_5_f45d09939527be362c586ae1d470afe4._comment7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_5_f45d09939527be362c586ae1d470afe4._comment b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_5_f45d09939527be362c586ae1d470afe4._comment
new file mode 100644
index 000000000..4fbbfe1ca
--- /dev/null
+++ b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_5_f45d09939527be362c586ae1d470afe4._comment
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="pot"
+ subject="Same issue"
+ date="2016-07-25T18:23:13Z"
+ content="""
+Anyone got any ideas on how to fix this, or move forward without starting again and trashing the gcrypt repos? Bit of a serious bug this, if it can't be repaired. I was using git-annex for backups, but finding your backups are corrupt would be a bit of a nightmare!
+"""]]