From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: Ralf Thielow <ralf.thielow@googlemail.com>
Cc: spearce@spearce.org, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] completion: --list option for git-branch
Date: Thu, 16 Feb 2012 10:28:42 +0100 [thread overview]
Message-ID: <4F3CCC4A.5010100@in.waw.pl> (raw)
In-Reply-To: <1329338218-9822-1-git-send-email-ralf.thielow@googlemail.com>
On 02/15/2012 09:36 PM, Ralf Thielow wrote:
> Signed-off-by: Ralf Thielow<ralf.thielow@googlemail.com>
> ---
> contrib/completion/git-completion.bash | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index d7367e9..1505cff 100755
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -1137,7 +1137,7 @@ _git_branch ()
> __gitcomp "
> --color --no-color --verbose --abbrev= --no-abbrev
> --track --no-track --contains --merged --no-merged
> - --set-upstream --edit-description
> + --set-upstream --edit-description --list
> "
> ;;
> *)
Normally one would use just a bare 'git branch' to list branches.
Why would you want to use --list in an interactive environment (as
opposed to a script)? Isn't it better not to clutter the completion
options with something that the user actually has not need for?
Zbyszek
next prev parent reply other threads:[~2012-02-16 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 20:36 [PATCH] completion: --list option for git-branch Ralf Thielow
2012-02-16 9:28 ` Zbigniew Jędrzejewski-Szmek [this message]
2012-02-16 18:07 ` Junio C Hamano
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=4F3CCC4A.5010100@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ralf.thielow@googlemail.com \
--cc=spearce@spearce.org \
/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