Re: [PATCH] bash completion: offer more options for gitk

From: Santi Béjar <santi@agolina.net>
Date: Feb 15, 2009, 09:56 UTC
Message-ID: <adf1fd3d0902150156w67a16e6fp3c946446c5ae2bfd@mail.gmail.com>
In-Reply-To: <7vfxigniws.fsf@gitster.siamese.dyndns.org>

2009/2/15 Junio C Hamano <gitster@pobox.com>:

Show 8 quoted lines

> Many options you add here are useful for git-log and not present in its
> completion, but as you point out not all git-log options necessarily make
> sense for gitk.  I think it would make sense to introduce an extra
> variable $__git_log_basic_options that holds the basic ones that can be in
> both, and add the ones that are specific to gitk or git-log in their own
> completion functions.  I suspect gitk's addition will be nil, while
> git-log would add --graph, --walk-reflogs and --no-merges to the basic
> set.

I sometimes use the --no-merges with gitk, normally within a range (the last 'next' update or so).

Santi

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.