mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
Cc: git <>
Subject: Re: [PATCH] Fix typo in Documentation/RelNotes/2.31.0.txt
Date: Fri, 14 May 2021 05:11:00 +0900	[thread overview]
Message-ID: <xmqqa6oybdij.fsf@gitster.g> (raw)
In-Reply-To: <> ('s message of "Thu, 13 May 2021 16:19:53 +0800")

"" <> writes:

> ping
> ---
>>From: Li Linchao <>
>>replace 'whey' with `when`
>>Signed-off-by: Li Linchao <>
>> Documentation/RelNotes/2.31.0.txt | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>diff --git a/Documentation/RelNotes/2.31.0.txt b/Documentation/RelNotes/2.31.0.txt
>>index cf0c7d8d40..617d211f3f 100644
>>--- a/Documentation/RelNotes/2.31.0.txt
>>+++ b/Documentation/RelNotes/2.31.0.txt
>>@@ -49,7 +49,7 @@ UI, Workflows & Features
>>    @{1}, but we failed to answer "what commit were we on?", i.e. @{1}
>>  * "git bundle" learns "--stdin" option to read its refs from the
>>-   standard input.  Also, it now does not lose refs whey they point
>>+   standard input.  Also, it now does not lose refs when they point
>>    at the same object.
>>  * "git log" learned a new "--diff-merges=<how>" option.

Thanks.  Will see if it makes sense to apply.

While it is true that is a typo, fixing it here won't correct it for
the 2.31 release as it was tagged and released long time ago.  And
of course, it will be silly to issue 2.31.1 maintenance release to
fix a typo in the release notes for 2.31.0 release.  So...

  reply	other threads:[~2021-05-13 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07  6:26 [PATCH] Fix typo in Documentation/RelNotes/2.31.0.txt lilinchao
2021-05-13  8:19 ` lilinchao
2021-05-13 20:11   ` Junio C Hamano [this message]
2021-05-13  9:39 ` Bagas Sanjaya

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:

  List information:

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

  git send-email \
    --in-reply-to=xmqqa6oybdij.fsf@gitster.g \ \ \ \

* 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

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).