close

2 files changed, 20 insertions, 0 deletions

diff --git a/doc/bugs/Can__39__t_keep_gpg_quiet.mdwn b/doc/bugs/Can__39__t_keep_gpg_quiet.mdwn
index 89158889d..b9b254343 100644
--- a/doc/bugs/Can__39__t_keep_gpg_quiet.mdwn
+++ b/doc/bugs/Can__39__t_keep_gpg_quiet.mdwn
@@ -42,3 +42,5 @@ I still get the output, which I shouldn't@
 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
 
 Mixed bag, works when it works, but I've had quite a few "unexplained" happenings. Perservering for now, hoping me reporting bugs will see things improve...
+
+> [[done]]; gcrypt.gpg-args is the answer. --[[Joey]] 
diff --git a/doc/bugs/Can__39__t_keep_gpg_quiet/comment_1_ab0ffdf17fb5caf8db70b77220878a1b._comment b/doc/bugs/Can__39__t_keep_gpg_quiet/comment_1_ab0ffdf17fb5caf8db70b77220878a1b._comment
new file mode 100644
index 000000000..5e6b231e8
--- /dev/null
+++ b/doc/bugs/Can__39__t_keep_gpg_quiet/comment_1_ab0ffdf17fb5caf8db70b77220878a1b._comment
@@ -0,0 +1,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.
+"""]]