From: Junio C Hamano <gitster@pobox.com>
To: "Zakariyah Ali via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Zakariyah Ali <zakariyahali100@gmail.com>
Subject: Re: [PATCH v3 0/2] completion: hide dotfiles for selected path completion
Date: Sat, 20 Jun 2026 18:17:54 -0700 [thread overview]
Message-ID: <xmqq1pe0g08t.fsf@gitster.g> (raw)
In-Reply-To: <pull.2311.v3.git.git.1781978156.gitgitgadget@gmail.com> (Zakariyah Ali via GitGitGadget's message of "Sat, 20 Jun 2026 17:55:54 +0000")
"Zakariyah Ali via GitGitGadget" <gitgitgadget@gmail.com> writes:
> The completion helper for index paths uses git ls-files rather than shell
> filename completion. As a result, leading-dot paths such as a tracked
> .gitignore were offered even when the user had not started the path with ..
>
> Hide leading-dot path components for git rm, git mv, and git ls-files when
> completing an empty path component. Explicit dot completion is still
> preserved, so git rm . can still complete .gitignore.
>
> This removes the existing TODO expectations in t/t9902-completion.sh and
> adds coverage for explicit dot completion.
OK.
> Validation:
>
> * git diff --check -- contrib/completion/git-completion.bash
> t/t9902-completion.sh
> * bash -n contrib/completion/git-completion.bash
> * ./t9902-completion.sh
I am not sure what you wanted to say with these lines. If you did
the above to build confidence that your patch works, that would be
great. Or are you telling readers to do these things and when they
do not see any issues consider your patch perfect?
What is missing around here in this cover letter is a description of
how this iteration is different from the previous one. And ...
> Zakariyah Ali (2):
> completion: hide dotfiles for selected path completion
> completion: hide dotfiles by default for path completion
>
> contrib/completion/git-completion.bash | 53 +++++++++++++++-----------
> t/t9902-completion.sh | 19 ++++-----
> 2 files changed, 40 insertions(+), 32 deletions(-)
>
>
> base-commit: 9b7fa37559a1b95ee32e32858b0d038b4cf583e5
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2311%2Falibaba0010%2Fcompletion-hide-dotfiles-v3
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2311/alibaba0010/completion-hide-dotfiles-v3
> Pull-Request: https://github.com/git/git/pull/2311
>
> Range-diff vs v2:
>
> 1: 056e239e06 = 1: 056e239e06 completion: hide dotfiles for selected path completion
> -: ---------- > 2: 7482ee4645 completion: hide dotfiles by default for path completion
... I find this range diff very troubling. If we look at patch 2,
it seems that it redoes some part of what is done in patch 1 saying
"oops that was wrong, so let's do it better this time". Such a
drunken-mans' walk that goes in one direction in an earlier step,
only to be corrected to move to a different course, is now how we
want a new topic to be presented.
The end result may be much easier to read, mostly thanks to updated
loop in the awk script, so if we really want to pretend this as two
patches for "small pieces are easier to digest" value, perhaps have
[PATCH 1/2] that updates the awk script (without doing anything
related to hide-dotfiles theme) to make it easier to read by not
having multiple "print pfx p" in it, and then build on top of that
improved base, have [PATCH 2/2] that adds the support to hide
dotfiles, perhaps?
Since the initial iteration was quite a while ago, I no longer
remember the details of the review I gave, but I recall having hard
time telling which callers of the complete-index-file helper hide
dotfiles from their output and which callers do not hide them, and
how the patch decided to choose which ones should and should not
hide. Has it been improved and if so how? That is something we
expect the cover letter to tell, too.
Thanks.
prev parent reply other threads:[~2026-06-21 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 2:36 [PATCH] completion: hide dotfiles for selected path completion Zakariyah Ali via GitGitGadget
2026-05-24 12:08 ` Junio C Hamano
2026-05-26 15:23 ` [PATCH v2] " Zakariyah Ali via GitGitGadget
2026-05-27 3:22 ` Junio C Hamano
2026-06-03 18:09 ` Follow-up and appreciation regarding Git contributions Zakariyah Ali
2026-06-10 18:56 ` [PATCH v2] completion: hide dotfiles for selected path completion Junio C Hamano
2026-06-20 17:55 ` [PATCH v3 0/2] " Zakariyah Ali via GitGitGadget
2026-06-20 17:55 ` [PATCH v3 1/2] " Zakariyah Ali via GitGitGadget
2026-06-20 17:55 ` [PATCH v3 2/2] completion: hide dotfiles by default for " Zakariyah Ali via GitGitGadget
2026-06-21 1:17 ` 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=xmqq1pe0g08t.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=zakariyahali100@gmail.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 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.