doc/config: mark ssh allowedSigners example as literal

The discussion for gpg.ssh.allowedSignersFile shows an example string
that contains "user1@example.com,user2@example.com". Asciidoc thinks
these are real email addresses and generates "mailto" footnotes for
them. This makes the rendered content more confusing, as it has extra
"[1]" markers:

  The file consists of one or more lines of principals followed by an
  ssh public key. e.g.: user1@example.com[1],user2@example.com[2]
  ssh-rsa AAAAX1... See ssh-keygen(1) "ALLOWED SIGNERS" for details.

and also generates pointless notes at the end of the page:

  NOTES
        1. user1@example.com
           mailto:user1@example.com

        2. user2@example.com
           mailto:user2@example.com

We can fix this by putting the example into a backtick literal block.
That inhibits the mailto generation, and as a bonus typesets the example
text in a way that sets it off from the regular prose (a tt font for
html, or bold in the roff manpage).

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Jeff King
2021-12-15 11:23:48 -05:00
committed by Junio C Hamano
parent e773545c7f
commit acd78728bb

View File

@ -44,7 +44,7 @@ gpg.ssh.allowedSignersFile::
A file containing ssh public keys which you are willing to trust. A file containing ssh public keys which you are willing to trust.
The file consists of one or more lines of principals followed by an ssh The file consists of one or more lines of principals followed by an ssh
public key. public key.
e.g.: user1@example.com,user2@example.com ssh-rsa AAAAX1... e.g.: `user1@example.com,user2@example.com ssh-rsa AAAAX1...`
See ssh-keygen(1) "ALLOWED SIGNERS" for details. See ssh-keygen(1) "ALLOWED SIGNERS" for details.
The principal is only used to identify the key and is available when The principal is only used to identify the key and is available when
verifying a signature. verifying a signature.