From: Azeem Bande-Ali <me@azeemba.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2021, #06; Mon, 16)
Date: Mon, 16 Aug 2021 19:43:58 -0400 [thread overview]
Message-ID: <CABye914RbBQEhSmdT+9oC_AYBpn-sfGySXqhV7uamry1Bs0tpQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqv945ng61.fsf@gitster.g>
On Mon, Aug 16, 2021 at 7:06 PM Junio C Hamano <gitster@pobox.com> wrote:
> * ab/help-autocorrect-prompt (2021-08-14) 1 commit
> - help.c: help.autocorrect=prompt waits for user action
>
> The logic for auto-correction of misspelt subcommands learned to go
> interactive when the help.autocorrect configuration variable is set
> to true.
Just a minor correction, the help.autocorrect configuration variable
has to be set to "prompt" for this behavior.
I wasn't sure if this description is propagated further (like in a
changelog) so thought it was better to point it out.
next prev parent reply other threads:[~2021-08-16 23:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 23:06 What's cooking in git.git (Aug 2021, #06; Mon, 16) Junio C Hamano
2021-08-16 23:43 ` Azeem Bande-Ali [this message]
2021-08-17 16:39 ` Junio C Hamano
2021-08-17 10:20 ` Phillip Wood
2021-08-17 17:00 ` Philippe Blain
2021-08-17 19:40 ` Junio C Hamano
[not found] ` <20210817193255.e7-9qhD5EZyGJNFbpSx2zPp6pXXRq5aMFbInG-_RoCk@z>
2021-08-17 19:32 ` Junio C Hamano
2021-08-17 17:12 ` Derrick Stolee
2021-08-18 5:15 ` Eric Sunshine
2021-08-19 10:06 ` Phillip Wood
2021-08-17 21:48 ` Junio C Hamano
2021-08-19 18:55 ` Phillip Wood
2021-08-19 19:38 ` Junio C Hamano
2021-08-20 6:09 ` Giving priority to the reftable topic (was Re: What's cooking in git.git (Aug 2021, #06; Mon, 16)) Junio C Hamano
2021-08-20 22:08 ` Ramsay Jones
2021-10-07 17:27 ` Han-Wen Nienhuys
[not found] ` <CACBZZX41gwo=pv_4fn2VcLz0Qq7Av-CWsnNXfXSuzmwZnu-Q3w@mail.gmail.com>
2021-08-23 10:21 ` Ævar Arnfjörð Bjarmason
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=CABye914RbBQEhSmdT+9oC_AYBpn-sfGySXqhV7uamry1Bs0tpQ@mail.gmail.com \
--to=me@azeemba.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).