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

Re: [PATCH 1/2] parse-options: Add support for dumping out long options

From
Stephen Boyd <bebarino@gmail.com>
Date
Apr 12, 2012, 07:02 UTC
Message-ID
<4F867E04.8000501@gmail.com>
In-Reply-To
<20120411125921.GC3161@burratino>
On 04/11/2012 05:59 AM, Jonathan Nieder wrote:
Show 24 quoted lines
> Stephen Boyd wrote:
> 
>> The bash completion script wants to know what the long options are for a
>> certain command at runtime. Add a magical long option that nobody could
>> possibly ever use (--dump-raw-long-options) to get this information.
> 
> Neat.  Probably should be documented:
> 
> diff --git i/Documentation/gitcli.txt w/Documentation/gitcli.txt
> index f734f97b..0de074ec 100644
> --- i/Documentation/gitcli.txt
> +++ w/Documentation/gitcli.txt
> @@ -96,6 +96,11 @@ usage: git describe [options] <committish>*
>  	are deprecated, and such options are hidden from the default usage. This
>  	option gives the full list of options.
>  
> +--dump-raw-long-options::
> +	prints a space-separated list of supported options, including
> +	negated `--no-<foo>` forms.  Long options taking an argument are
> +	printed with a trailing equal sign, as in "`--depth=`".
> +
>  
>  Negating options
>  ~~~~~~~~~~~~~~~~
Thanks. Squashed in.
Previous: Jonathan NiederNext: SZEDER Gábor
Message 6 of 14 in “Dynamic long options for bash completion”
  1. 0/2 Dynamic long options for bash completionStephen Boyd, Apr 11, 2012
  2. 1/2 parse-options: Add support for dumping out long optionsStephen Boyd, Apr 11, 2012
  3. Felipe ContrerasApr 11, 2012
  4. Stephen BoydApr 12, 2012
  5. Jonathan NiederApr 11, 2012
  6. Stephen BoydApr 12, 2012
  7. SZEDER GáborApr 11, 2012
  8. Stephen BoydApr 12, 2012
  9. SZEDER GáborApr 15, 2012
  10. Junio C HamanoApr 15, 2012
  11. 2/2 completion: Use parse-options raw output for simple long optionsStephen Boyd, Apr 11, 2012
  12. Jonathan NiederApr 11, 2012
  13. SZEDER GáborApr 11, 2012
  14. SZEDER GáborApr 17, 2012

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.