mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <>
To: Ondrej Pohorelsky <>
Subject: Re: Bash-completion missing option merge-base
Date: Fri, 17 Jan 2020 14:42:04 +0100 (CET)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

Hi Ondřej,

On Fri, 17 Jan 2020, Ondrej Pohorelsky wrote:

> We have encountered a bug where merge-base is missing in bash
> completion. [1]

The `merge-base` command is not considered a user-facing command:
(the "plumbing" in "plumbinginterrogators" means that this is supposed to
be a low-level command, to be used in scripts, but not so much

Therefore I think that it is intentional that this command does not
tab-complete: to declutter the list when typing git<TAB><TAB>.


      reply	other threads:[~2020-01-17 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 13:29 Bash-completion missing option merge-base Ondrej Pohorelsky
2020-01-17 13:42 ` Johannes Schindelin [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:

  List information:

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

  git send-email \ \ \ \ \

* 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

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).