From: Andrey <butirsky@gmail.com>
To: git@vger.kernel.org
Subject: bash completion bug: git range-diff: no --diff-merges option
Date: Fri, 13 Mar 2026 23:36:17 +0300 [thread overview]
Message-ID: <2c9651da-6c1c-471a-a239-5a60576251a6@gmail.com> (raw)
--diff-merges=, --no-diff-merges, --remerge-diff valuable options are
absent for 'git range-diff' completion.
These are the options presented here:
|# Options accepted by log and show
__git_log_show_options="
--diff-merges --diff-merges= --no-diff-merges --dd --remerge-diff
--encoding=
"|
But they are not included for range-diff:
|_git_range_diff ()
{
case "$cur" in
--*)
__gitcomp "
--creation-factor= --no-dual-color
$__git_diff_common_options
"
return
;;
esac
__git_complete_revlist
}|
[System Info]
git version 2.53.0
reply other threads:[~2026-03-13 20:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2c9651da-6c1c-471a-a239-5a60576251a6@gmail.com \
--to=butirsky@gmail.com \
--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