From ef681321a90a255e572b0be9d807dd072ce7489b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 21 Sep 2016 17:53:59 -0400 Subject: [PATCH] comment --- ...10_9d4fdddd7ab05de9dfa4cc90f1051ef5._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_10_9d4fdddd7ab05de9dfa4cc90f1051ef5._comment 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 0000000000..2bb9552ff2 --- /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. +"""]]