summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Robert Morgan <robert.thomas.morgan@gmail.com>2019-07-12 08:33:57 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-07-12 11:14:22 -0700
commitf7bf24d4dde9b5ff1bded664864feb7afb7d1c6b (patch)
tree9fa4afdcf534e85645035d4cb2883b95ab448848 /Documentation
parentGit 2.20.1 (diff)
downloadtgif-f7bf24d4dde9b5ff1bded664864feb7afb7d1c6b.tar.xz
gpg(docs): use correct --verify syntax
The gpg --verify usage example within the 'gpg.program' variable reference provides an incorrect example of the gpg --verify command arguments. The command argument order, when providing both a detached signature and data, should be signature first and data second: https://gnupg.org/documentation/manuals/gnupg/Operational-GPG-Commands.html Signed-off-by: Robert Morgan <robert.thomas.morgan@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/config/gpg.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/config/gpg.txt b/Documentation/config/gpg.txt
index 590fe0d4ba..5378a528b0 100644
--- a/Documentation/config/gpg.txt
+++ b/Documentation/config/gpg.txt
@@ -2,7 +2,7 @@ gpg.program::
Use this custom program instead of "`gpg`" found on `$PATH` when
making or verifying a PGP signature. The program must support the
same command-line interface as GPG, namely, to verify a detached
- signature, "`gpg --verify $file - <$signature`" is run, and the
+ signature, "`gpg --verify $signature - <$file`" is run, and the
program is expected to signal a good signature by exiting with
code 0, and to generate an ASCII-armored detached signature, the
standard input of "`gpg -bsau $key`" is fed with the contents to be