git@vger.kernel.org mailing list mirror (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
Subject: Re: [PATCH] Documentation/RelNotes: fix a typo in 2.28's relnotes
Date: Wed, 22 Jul 2020 14:10:05 -0700	[thread overview]
Message-ID: <xmqq1rl35k9e.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <e78abce653d4bf13b9fb464db3d8ecf6b7d137b2.1595449743.git.me@ttaylorr.com> (Taylor Blau's message of "Wed, 22 Jul 2020 16:29:40 -0400")

Taylor Blau <me@ttaylorr.com> writes:

> Signed-off-by: Taylor Blau <me@ttaylorr.com>
> ---
>
> Just a small typo that I noticed while reading the release notes for
> GitHub's blog post about it.

Thanks.

>
>  Documentation/RelNotes/2.28.0.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RelNotes/2.28.0.txt b/Documentation/RelNotes/2.28.0.txt
> index 5f1413a699..6baf781380 100644
> --- a/Documentation/RelNotes/2.28.0.txt
> +++ b/Documentation/RelNotes/2.28.0.txt
> @@ -116,7 +116,7 @@ Performance, Internal Implementation, Development Support etc.
>     configuration variables in extensions.* namespace were supposed to
>     have special meaning in repositories whose version numbers are 1 or
>     higher), but this was a bit too big a change.  The behaviour in
> -   recent versions of Git where certaion extensions.* were honored by
> +   recent versions of Git where certain extensions.* were honored by
>     mistake even in version 0 repositories has been restored.
>
>
> --
> 2.28.0.rc1.13.ge78abce653

      reply	other threads:[~2020-07-22 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 20:29 [PATCH] Documentation/RelNotes: fix a typo in 2.28's relnotes Taylor Blau
2020-07-22 21:10 ` 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=xmqq1rl35k9e.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.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 public 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).