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

Re: [PATCH 1/2] docs: clarify git-branch --list behavior

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 1, 2013, 00:37 UTC
Message-ID
<7v4nhweuoi.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAPig+cT21Fx6BaD=1jT7KSBZSZkWu-A-0U+QsM2qO8g5gki=YQ@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
Show 10 quoted lines
> On Thu, Jan 31, 2013 at 1:45 AM, Jeff King <peff@peff.net> wrote:
>> +If `--list` is given, or if there are no non-option arguments, existing
>> +branches are listed; the current branch will be highlighted with an
>> +asterisk.  Option `-r` causes the remote-tracking branches to be listed,
>> +and option `-a` shows both local and remote branches. If a `<pattern>`
>> +is given, it is used as a shell wildcard to restrict the output to
>> +matching branches. If multiple patterns are given, a branch is shown if
>> +any it is matched by any of the patterns.
>
> s/if any it is/if it is/
Thanks; I'll squash this in.  Peff, no need to resend.
 Documentation/git-branch.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index 01aa87f..2635dee 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -28,7 +28,7 @@ asterisk.  Option `-r` causes the remote-tracking branches to be listed,
 and option `-a` shows both local and remote branches. If a `<pattern>`
 is given, it is used as a shell wildcard to restrict the output to
 matching branches. If multiple patterns are given, a branch is shown if
-any it is matched by any of the patterns.  Note that when providing a
+it matches any of the patterns.  Note that when providing a
 `<pattern>`, you must use `--list`; otherwise the command is interpreted
 as branch creation.
 
Previous: Eric SunshineNext: Jeff King
Message 5 of 11 in “[BUG] `git branch --contains ID name` creates branch "name"”
  1. Peter WuJan 30, 2013
  2. 0/2 improve "git branch --contains=<commit> <pattern>"Jeff King, Jan 31, 2013
  3. 1/2 docs: clarify git-branch --list behaviorJeff King, Jan 31, 2013
  4. Eric SunshineFeb 1, 2013
  5. Junio C HamanoFeb 1, 2013
  6. Jeff KingFeb 1, 2013
  7. Junio C HamanoFeb 1, 2013
  8. 2/2 branch: let branch filters imply --listJeff King, Jan 31, 2013
  9. Peter WuJan 31, 2013
  10. Junio C HamanoJan 31, 2013
  11. Junio C HamanoJan 31, 2013

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.