git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 0/7] completion bash: add more options and commands

From
Johannes Sixt <j6t@kdbg.org>
Date
Feb 7, 2017, 09:00 UTC
Message-ID
<5c8d6f15-e37f-f92f-5eb3-2e6224b2a92f@kdbg.org>
In-Reply-To
<xmqqd1ev100b.fsf@gitster.mtv.corp.google.com>
Am 06.02.2017 um 22:29 schrieb Junio C Hamano:
Show 14 quoted lines
> cornelius.weig@tngtech.com writes:
>
>> From: Cornelius Weig <cornelius.weig@tngtech.com>
>>
>> This is the re-roll of patch series <20170122225724.19360-1-cornelius.weig@tngtech.com>.
>>
>> This patch series adds all long-options that are mentioned in the synopsis of
>> the man-page for the respective git-command. There are only a few exceptions,
>> as discussed in the above thread. For example, no unsafe options should be
>> completed.
>> Furthermore, the patches add subommand option completion for git-submodule and
>> git-remote.
>
> Reviewers, do these look good now?
My concerns have been addressed. The patches look good from a cursory read.
-- Hannes
Previous: Junio C Hamano
Message 10 of 10 in “completion bash: add more options and commands”
  1. 0/7 completion bash: add more options and commandscornelius.weig@tngtech.com, Feb 3, 2017
  2. 3/7 completion: improve bash completion for git-addcornelius.weig@tngtech.com, Feb 3, 2017
  3. 4/7 completion: teach ls-remote to complete optionscornelius.weig@tngtech.com, Feb 3, 2017
  4. 7/7 completion: recognize more long-optionscornelius.weig@tngtech.com, Feb 3, 2017
  5. 5/7 completion: teach replace to complete optionscornelius.weig@tngtech.com, Feb 3, 2017
  6. 6/7 completion: teach remote subcommands to complete optionscornelius.weig@tngtech.com, Feb 3, 2017
  7. 1/7 completion: teach submodule subcommands to complete optionscornelius.weig@tngtech.com, Feb 3, 2017
  8. 2/7 completion: add subcommand completion for rererecornelius.weig@tngtech.com, Feb 3, 2017
  9. Junio C HamanoFeb 6, 2017
  10. Johannes SixtFeb 7, 2017

Read the whole thread, see it on lore, or plain text.

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