From: Junio C Hamano <gitster@pobox.com>
To: "Robert Estelle via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Robert Estelle <robertestelle@gmail.com>,
Robert Estelle <robert.estelle@gmail.com>
Subject: Re: [PATCH v2] completion: fix incorrect bash/zsh string equality check
Date: Thu, 28 Oct 2021 09:36:33 -0700 [thread overview]
Message-ID: <xmqq8rydt8by.fsf@gitster.g> (raw)
In-Reply-To: <pull.1096.v2.git.git.1635200973354.gitgitgadget@gmail.com> (Robert Estelle via GitGitGadget's message of "Mon, 25 Oct 2021 22:29:33 +0000")
"Robert Estelle via GitGitGadget" <gitgitgadget@gmail.com> writes:
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index 4bdd27ddc87..8ca9b15f21d 100644
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -515,7 +515,7 @@ __gitcomp_file ()
> # argument, and using the options specified in the second argument.
> __git_ls_files_helper ()
> {
> - if [ "$2" == "--committable" ]; then
> + if [ "$2" = "--committable" ]; then
> __git -C "$1" -c core.quotePath=false diff-index \
> --name-only --relative HEAD -- "${3//\\/\\\\}*"
> else
>
> base-commit: 225bc32a989d7a22fa6addafd4ce7dcd04675dbf
Thanks. We can trace this back to April 2013, if not earlier. It
is sort of surprising that nobody else has noticed it since then
X-<.
Will queue. Thanks, again.
prev parent reply other threads:[~2021-10-28 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 21:39 [PATCH] completion: fix incorrect bash/zsh string equality check Robert Estelle via GitGitGadget
2021-10-08 20:50 ` Junio C Hamano
2021-10-08 20:57 ` brian m. carlson
2021-10-08 22:17 ` Robert Estelle
2021-10-08 22:05 ` Robert Estelle
2021-10-08 22:16 ` Junio C Hamano
2021-10-08 22:26 ` Robert Estelle
2021-10-08 23:09 ` Junio C Hamano
2021-10-25 22:20 ` Robert Estelle
2021-10-25 22:29 ` [PATCH v2] " Robert Estelle via GitGitGadget
2021-10-28 16:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8rydt8by.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=robert.estelle@gmail.com \
--cc=robertestelle@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.