comment
authorJoey Hess <joeyh@joeyh.name>
Tue, 24 Aug 2021 15:57:51 +0000 (11:57 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 24 Aug 2021 15:57:51 +0000 (11:57 -0400)
doc/bugs/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_1_0351276d5eeb5d8af0cf0e72c3a213fd._comment [new file with mode: 0644]

diff --git a/doc/bugs/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_1_0351276d5eeb5d8af0cf0e72c3a213fd._comment b/doc/bugs/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_1_0351276d5eeb5d8af0cf0e72c3a213fd._comment
new file mode 100644 (file)
index 0000000..cff0017
--- /dev/null
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2021-08-24T15:54:15Z"
+ content="""
+It already ignores nonzero exit status of that command, since
+old gpg's don't support it.
+
+So, it must not really be the `gpgconf --kill` that is causing the test
+failure.
+
+Please post the actual test failure message.
+"""]]