summaryrefslogtreecommitdiff
path: root/doc/bugs/Can__39__t_keep_gpg_quiet/comment_1_ab0ffdf17fb5caf8db70b77220878a1b._comment
blob: 5e6b231e8d35a5df87ed11aaa07925f2659563b5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
[[!comment format=mdwn
 username="joey"
 subject="""comment 1"""
 date="2016-10-17T20:32:02Z"
 content="""
The gnupg-options and gnupg-decrypt-options only apply when git-annex
is running gpg, not when git-annex is running git push which is running
git-remote-gcrypt which is running gpg.

I don't think there's any way to pass gpg options through that chain of
programs. Even if there is, I don't know that it would make sense to use
the git-annex configuration, which normally is used when git-annex is using
gpg in symmetric encryption mode, for git-remote-gcrypt, which is using gpg
in pubic key encryption mode.

I think you should just set gcrypt.gpg-args to whatever options are
appropriate for its use of gpg.
"""]]