git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, derrickstolee@github.com, avarab@gmail.com
Subject: Re: [PATCH] Documentation/config/transfer.txt: fix typo
Date: Thu, 23 Jun 2022 12:42:17 -0700	[thread overview]
Message-ID: <xmqqa6a3yxnq.fsf@gitster.g> (raw)
In-Reply-To: <68c1c3648c51f6298eea4d58286b20e0c770a270.1656010900.git.me@ttaylorr.com> (Taylor Blau's message of "Thu, 23 Jun 2022 15:02:01 -0400")

Taylor Blau <me@ttaylorr.com> writes:

> Commit 7281c196b1 (transfer doc: move fetch.credentialsInUrl to
> "transfer" config namespace, 2022-06-15) propagates a typo from
> 6dcbdc0d66 (remote: create fetch.credentialsInUrl config, 2022-06-06),
> where "other" is misspelled as "oher". Fix the typo accordingly.
>
> Signed-off-by: Taylor Blau <me@ttaylorr.com>
> ---
> Noticed while skimming the new documentation for the upcoming 2.37
> release.

Thanks.

>
>  Documentation/config/transfer.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/config/transfer.txt b/Documentation/config/transfer.txt
> index b4475c0690..7ed917f5fc 100644
> --- a/Documentation/config/transfer.txt
> +++ b/Documentation/config/transfer.txt
> @@ -20,7 +20,7 @@ exposure, e.g. because:
>    in other ways, e.g. a backup process might copy the data to another
>    system.
>  * The git programs will pass the full URL to one another as arguments
> -  on the command-line, meaning the credentials will be exposed to oher
> +  on the command-line, meaning the credentials will be exposed to other
>    users on OS's or systems that allow other users to see the full
>    process list of other users. On linux the "hidepid" setting
>    documented in procfs(5) allows for configuring this behavior.
> --
> 2.35.1

      reply	other threads:[~2022-06-23 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 19:02 Taylor Blau
2022-06-23 19:42 ` Junio C Hamano [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqa6a3yxnq.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    /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.
Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).