diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-09-21 17:53:59 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-09-21 17:53:59 -0400 |
| commit | f8aae8bb43eef2abab628ded28844523f1ce4f2a (patch) | |
| tree | c9bd893f3aec27f0940931f9f4eefd06852635a2 | |
| parent | 9e68a37df6484d31597df5fd380d0b0871d1726f (diff) | |
comment
| -rw-r--r-- | doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_10_9d4fdddd7ab05de9dfa4cc90f1051ef5._comment | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_10_9d4fdddd7ab05de9dfa4cc90f1051ef5._comment b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_10_9d4fdddd7ab05de9dfa4cc90f1051ef5._comment new file mode 100644 index 000000000..2bb9552ff --- /dev/null +++ b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_10_9d4fdddd7ab05de9dfa4cc90f1051ef5._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 10""" + date="2016-09-21T21:36:18Z" +content=""" +@Don and @pot, did you actually see un-encrypted data end up in the gcrypt +repository? Or by "same issue" do you mean you saw the same error message, +perhaps due to a very different cause? + +@jgoerzen, when you say that the gcrypt reposotory had an "unencrypted +index", are you referring to a regular git index file, or to a pack's .idx +file? + +It would be very strange if a gcrypt repository had an index file. +I've never been able to use git-remote-gcrypt with a non-bare repository, +and bare repositories don't normally have index files. +"""]] |