git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Philippe Blain <levraiphilippeblain@gmail.com>,
	Philippe Blain <levraiphilippeblain@gmail.com>
Subject: [PATCH 3/4] completion: complete --encoding
Date: Sun, 21 Jan 2024 04:07:50 +0000	[thread overview]
Message-ID: <faa601ecb92b301d5730474efd11fba27d6a5cc7.1705810072.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1650.git.git.1705810071.gitgitgadget@gmail.com>

From: Philippe Blain <levraiphilippeblain@gmail.com>

The option --encoding is supported by 'git log' and 'git show', so add
it to __git_log_show_options.

Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
---
 contrib/completion/git-completion.bash | 1 +
 1 file changed, 1 insertion(+)

diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index ccb17f4ad7b..a7ae2cbe55b 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -2096,6 +2096,7 @@ __git_log_shortlog_options="
 # Options accepted by log and show
 __git_log_show_options="
 	--diff-merges --diff-merges= --no-diff-merges --dd --remerge-diff
+	--encoding=
 "
 
 __git_diff_merges_opts="off none on first-parent 1 separate m combined c dense-combined cc remerge r"
-- 
gitgitgadget


  parent reply	other threads:[~2024-01-21  4:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21  4:07 [PATCH 0/4] completion: add missing 'git log' options Philippe Blain via GitGitGadget
2024-01-21  4:07 ` [PATCH 1/4] completion: complete missing rev-list options Philippe Blain via GitGitGadget
2024-01-21  4:07 ` [PATCH 2/4] completion: complete --patch-with-raw Philippe Blain via GitGitGadget
2024-01-22 16:09   ` Junio C Hamano
2024-01-21  4:07 ` Philippe Blain via GitGitGadget [this message]
2024-01-21  4:07 ` [PATCH 4/4] completion: complete missing 'git log' options Philippe Blain via GitGitGadget

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=faa601ecb92b301d5730474efd11fba27d6a5cc7.1705810072.git.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=levraiphilippeblain@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 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).