From: Stephen Boyd <bebarino@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, spearce@spearce.org, szeder@ira.uka.de,
felipe.contreras@gmail.com
Subject: Re: [PATCH 1/2] parse-options: Add support for dumping out long options
Date: Thu, 12 Apr 2012 00:02:28 -0700 [thread overview]
Message-ID: <4F867E04.8000501@gmail.com> (raw)
In-Reply-To: <20120411125921.GC3161@burratino>
On 04/11/2012 05:59 AM, Jonathan Nieder wrote:
> 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.
next prev parent reply other threads:[~2012-04-12 7:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 10:29 [PATCH 0/2] Dynamic long options for bash completion Stephen Boyd
2012-04-11 10:29 ` [PATCH 1/2] parse-options: Add support for dumping out long options Stephen Boyd
2012-04-11 10:51 ` Felipe Contreras
2012-04-12 7:42 ` Stephen Boyd
2012-04-11 12:59 ` Jonathan Nieder
2012-04-12 7:02 ` Stephen Boyd [this message]
2012-04-11 14:06 ` SZEDER Gábor
2012-04-12 7:12 ` Stephen Boyd
2012-04-15 12:49 ` SZEDER Gábor
2012-04-15 19:23 ` Junio C Hamano
2012-04-11 10:29 ` [PATCH 2/2] completion: Use parse-options raw output for simple " Stephen Boyd
2012-04-11 13:09 ` Jonathan Nieder
2012-04-11 13:56 ` SZEDER Gábor
2012-04-17 10:44 ` SZEDER Gábor
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F867E04.8000501@gmail.com \
--to=bebarino@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=spearce@spearce.org \
--cc=szeder@ira.uka.de \
/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.
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 NNTP newsgroup(s).