@@ -34,7 +34,7 @@ gpg.minTrustLevel:: * `fully` * `ultimate`-gpg.ssh.defaultKeyCommand:+gpg.ssh.defaultKeyCommand:: This command that will be run when user.signingkey is not set and a ssh signature is requested. On successful exit a valid ssh public key is expected in the first line of its output. To automatically use the first
Thanks, this fix is "obviously correct".
Please add your Signed-off-by: at the end of the commit message.
Minor: The commit message could work just as well without mentioning a
particular site hosting documentation, so something like this would
also be fine:
Add missing colon to ensure correct rendering of definition list
item. Without the proper number of colons, it renders as just
another top-level paragraph rather than a list item.
@@ -34,7 +34,7 @@ gpg.minTrustLevel::-gpg.ssh.defaultKeyCommand:+gpg.ssh.defaultKeyCommand:: This command that will be run when user.signingkey is not set and a ssh signature is requested. On successful exit a valid ssh public key is expected in the first line of its output. To automatically use the first
If you want to tackle them, some other fixes would be:
* "This _is the_ command that..." or "This command will be..."
* in user-facing documentation, we use camelCase for configuration
names, so "user.signingkey" should be "user.signingKey"
* s/ssh/SSH/
* s/exit/exit,/
From: Eric Sunshine <hidden> Date: 2021-12-17 15:48:15
On Fri, Dec 17, 2021 at 10:44 AM Eric Sunshine [off-list ref] wrote:
quoted
+gpg.ssh.defaultKeyCommand::
This command that will be run when user.signingkey is not set and a ssh
signature is requested. On successful exit a valid ssh public key is
expected in the first line of its output. To automatically use the first
If you want to tackle them, some other fixes would be:
* "This _is the_ command that..." or "This command will be..."
* in user-facing documentation, we use camelCase for configuration
names, so "user.signingkey" should be "user.signingKey"
* s/ssh/SSH/
* s/exit/exit,/
Oh, I forgot to mention that we typically want to use backticks to
typeset text with fixed-width font for elements such as:
`user.signingKey`
`ssh-agent`
`ssh-add -L`
Just added a Signed-off-by and reworded the commit message
as suggested by Eric Sunshine. There are other fixes that could
be applied to other places in this documentation (eg. backticks,
capitalization fixes etc) but my intent here was just to fix the
most jarring problem.
Just added a Signed-off-by and reworded the commit message
as suggested by Eric Sunshine. There are other fixes that could
be applied to other places in this documentation (eg. backticks,
capitalization fixes etc) but my intent here was just to fix the
most jarring problem.
Just added a Signed-off-by and reworded the commit message
as suggested by Eric Sunshine. There are other fixes that could
be applied to other places in this documentation (eg. backticks,
capitalization fixes etc) but my intent here was just to fix the
most jarring problem.
Just added a Signed-off-by and reworded the commit message
as suggested by Eric Sunshine. There are other fixes that could
be applied to other places in this documentation (eg. backticks,
capitalization fixes etc) but my intent here was just to fix the
most jarring problem.
Add missing colon to ensure correct rendering of definition list
item. Without the proper number of colons, it renders as just another
top-level paragraph rather than a list item.
Signed-off-by: Greg Hurrell <redacted>
---
Documentation/config/gpg.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -34,7 +34,7 @@ gpg.minTrustLevel:: * `fully` * `ultimate`-gpg.ssh.defaultKeyCommand:+gpg.ssh.defaultKeyCommand:: This command that will be run when user.signingkey is not set and a ssh signature is requested. On successful exit a valid ssh public key is expected in the first line of its output. To automatically use the first
Sorry about all the duplicate messages sent previously — I
was dusting off `git send-email` for the first time in a long time
and thought they were dry runs, but evidently they were not.
🤦
On Fri, Dec 17, 2021, at 5:17 PM, Greg Hurrell wrote:
quoted hunk
Add missing colon to ensure correct rendering of definition list
item. Without the proper number of colons, it renders as just another
top-level paragraph rather than a list item.
Signed-off-by: Greg Hurrell <redacted>
---
Documentation/config/gpg.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
* `fully`
* `ultimate`
-gpg.ssh.defaultKeyCommand:
+gpg.ssh.defaultKeyCommand::
This command that will be run when user.signingkey is not set and a ssh
signature is requested. On successful exit a valid ssh public key is
expected in the first line of its output. To automatically use the first
--
2.33.0