From: "Rubén Justo" <rjusto@gmail.com>
To: Dragan Simic <dsimic@manjaro.org>, git@vger.kernel.org
Subject: Re: [PATCH] doc: note that interactive.singleKey is disabled by default
Date: Wed, 22 May 2024 19:31:19 +0200 [thread overview]
Message-ID: <f7cf64cc-1458-49db-979f-eb4c70223620@gmail.com> (raw)
In-Reply-To: <3141fe9f7328a97bf3818748421f6ae929120626.1716363167.git.dsimic@manjaro.org>
On Wed, May 22, 2024 at 09:34:16AM +0200, Dragan Simic wrote:
> Make it clear that the interactive.singleKey configuration option is disabled
> by default. This should eliminate any associated doubts.
>
> Signed-off-by: Dragan Simic <dsimic@manjaro.org>
> ---
> Documentation/config/interactive.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/config/interactive.txt b/Documentation/config/interactive.txt
> index 5cc26555f19a..067496d77cea 100644
> --- a/Documentation/config/interactive.txt
> +++ b/Documentation/config/interactive.txt
> @@ -5,6 +5,7 @@ interactive.singleKey::
> linkgit:git-add[1], linkgit:git-checkout[1],
> linkgit:git-restore[1], linkgit:git-commit[1],
> linkgit:git-reset[1], and linkgit:git-stash[1].
> + This is disabled by default.
I'm on the fence if it needs to be said explicitly. But, I'll add
that it has been so since it was introduced in ca6ac7f135 (add -p:
prompt for single characters, 2009-02-05).
Thank you for your attention to detail.
>
> interactive.diffFilter::
> When an interactive command (such as `git add --patch`) shows
next prev parent reply other threads:[~2024-05-22 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 7:34 [PATCH] doc: note that interactive.singleKey is disabled by default Dragan Simic
2024-05-22 17:31 ` Rubén Justo [this message]
2024-05-22 18:28 ` Junio C Hamano
2024-05-22 18:52 ` Dragan Simic
2024-05-22 20:45 ` Junio C Hamano
2024-05-22 20:50 ` Dragan Simic
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=f7cf64cc-1458-49db-979f-eb4c70223620@gmail.com \
--to=rjusto@gmail.com \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
/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).