summaryrefslogtreecommitdiff
path: root/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_10_9d4fdddd7ab05de9dfa4cc90f1051ef5._comment
blob: 2bb9552ff2b5cd6cd4f524e12984a1dcbd1f88e6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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.
"""]]