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

Re: [PATCH] completion: --list option for git-branch

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 16, 2012, 18:07 UTC
Message-ID
<7vpqdezm6u.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4F3CCC4A.5010100@in.waw.pl>
Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> writes:
> 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?
        $ git branch jc/\*
        fatal: 'jc/*' is not a valid branch name.
        $ git branch --list jc/\*
          jc/advise-i18n
          jc/advise-push-default
          ...
Previous: Zbigniew Jędrzejewski-Szmek
Message 3 of 3 in “completion: --list option for git-branch”
  1. completion: --list option for git-branchRalf Thielow, Feb 15, 2012
  2. Zbigniew Jędrzejewski-SzmekFeb 16, 2012
  3. Junio C HamanoFeb 16, 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.