All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Greg Hurrell <greg@hurrell.net>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH v2 1/2] Documentation/config/pgp.txt: replace stray <TAB> character with <SPC>
Date: Wed, 26 Jan 2022 18:30:29 -0800	[thread overview]
Message-ID: <xmqq5yq56hbu.fsf@gitster.g> (raw)
In-Reply-To: <20220126121426.53799-2-greg@hurrell.net> (Greg Hurrell's message of "Wed, 26 Jan 2022 13:14:25 +0100")

Greg Hurrell <greg@hurrell.net> writes:

> Specifically, replace the tab between "the" and "first" with a space.

Good eyes.  Does it have ANY practical downside to leave it unfixed?

In other words, how did you spot it (e.g. "asciidoctor passes tab as-is
and screwed up an alignment of the text, which was how I noticed it")?

Thanks.

>
> Signed-off-by: Greg Hurrell <greg@hurrell.net>
> ---
>  Documentation/config/gpg.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/config/gpg.txt b/Documentation/config/gpg.txt
> index 0cb189a077..abfabd6d62 100644
> --- a/Documentation/config/gpg.txt
> +++ b/Documentation/config/gpg.txt
> @@ -37,7 +37,7 @@ gpg.minTrustLevel::
>  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
> +	expected in the first line of its output. To automatically use the first
>  	available key from your ssh-agent set this to "ssh-add -L".
>  
>  gpg.ssh.allowedSignersFile::

  reply	other threads:[~2022-01-27  2:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 12:37 [PATCH 0/2] docs: apply minor fixes to Documentation/config/pgp.txt Greg Hurrell
2022-01-25 12:37 ` [PATCH 1/2] docs: Fix bad whitespace in Documentation/config/pgp.txt Greg Hurrell
2022-01-25 17:09   ` Ævar Arnfjörð Bjarmason
2022-01-26 12:14     ` [PATCH v2 0/2] Apply minor fixes to Documentation/config/pgp.txt Greg Hurrell
2022-01-26 12:14       ` [PATCH v2 1/2] Documentation/config/pgp.txt: replace stray <TAB> character with <SPC> Greg Hurrell
2022-01-27  2:30         ` Junio C Hamano [this message]
2022-01-27  8:20           ` Greg Hurrell
2022-01-27 17:50             ` Junio C Hamano
2022-01-26 12:14       ` [PATCH 2/2] Documentation/config/pgp.txt: add missing apostrophe Greg Hurrell
2022-01-27  2:30         ` Junio C Hamano
2022-01-25 12:37 ` [PATCH 2/2] docs: add missing apostrophe to Documentation/config/gpg.txt Greg Hurrell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq5yq56hbu.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=greg@hurrell.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.