git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Hadi Safari <hadi@hadisafari.ir>
To: Git Users <git@vger.kernel.org>
Subject: Incomplete bash completion on git commit: --allow-empty-message and --allow-empty
Date: Thu, 16 Aug 2018 12:16:51 +0430	[thread overview]
Message-ID: <69624916-f6ba-d4a4-e346-69498662905e@hadisafari.ir> (raw)

Hi!

I'm wondering why there isn't --allow-empty and --allow-empty-message in 
completeion list of git commit command. I'm getting only following flags 
from v2.18.0 on `git commit --`:

--ahead-behind      --include           --reedit-message=
--all               --interactive       --reset-author
--amend             --long              --reuse-message=
--author=           --message=          --short
--branch            --no-edit           --signoff
--cleanup=          --no-post-rewrite   --squash=
--date=             --no-verify         --status
--dry-run           --null              --template=
--edit              --only              --untracked-files
--file=             --patch             --verbose
--fixup=            --porcelain         --verify
--gpg-sign          --quiet

Besides, is there any way to allow empty commit message for a repo, e.g. 
by adding something to `.git/config`? I couldn't find any in docs.

-- 
Hadi

             reply	other threads:[~2018-08-16  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16  7:46 Hadi Safari [this message]
2018-08-16 15:10 ` Incomplete bash completion on git commit: --allow-empty-message and --allow-empty Duy Nguyen
2018-08-16 15:11 ` [PATCH] completion: include PARSE_OPT_HIDDEN in completion output Ævar Arnfjörð Bjarmason
2018-08-16 15:50   ` Junio C Hamano
2018-08-17 14:47   ` Duy Nguyen

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=69624916-f6ba-d4a4-e346-69498662905e@hadisafari.ir \
    --to=hadi@hadisafari.ir \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).