aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant
diff options
context:
space:
mode:
authorGravatar spwhitton <spwhitton@web>2016-08-09 20:17:48 +0000
committerGravatar admin <admin@branchable.com>2016-08-09 20:17:48 +0000
commit6a0e9a22bc9e0c33c84ad1bf97df4d7375006cdc (patch)
treea35611239f831bfc1882a1160d1065cbee646d53 /doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant
parentc8d4eab415e23c3cc54d347761a5f1c551e4a982 (diff)
Added a comment
Diffstat (limited to 'doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant')
-rw-r--r--doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_9_16c004fe7c77cbbba113787ce6410c9e._comment9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_9_16c004fe7c77cbbba113787ce6410c9e._comment b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_9_16c004fe7c77cbbba113787ce6410c9e._comment
new file mode 100644
index 000000000..6c7624122
--- /dev/null
+++ b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_9_16c004fe7c77cbbba113787ce6410c9e._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="spwhitton"
+ subject="comment 9"
+ date="2016-08-09T20:17:47Z"
+ content="""
+I'm the git-remote-gcrypt maintainer, but as it stands it's not really possible to do anything about this bug without steps to reliably reproduce the corrupted/unencrypted remote repository.
+
+I have been using git-remote-gcrypt with git-annex and with plain git repos for more than two years and I have never encountered anything like this issue. So there's no starting point to work on a fix for the issue.
+"""]]