projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 045e388) | patch
docs: clarify git-branch --list behavior
authorJeff King <peff@peff.net>
Thu, 31 Jan 2013 06:45:46 +0000 (01:45 -0500)
committerJunio C Hamano <gitster@pobox.com>
Fri, 1 Feb 2013 00:37:16 +0000 (16:37 -0800)
commitde90ff81f3bba50776b934842112eeb6e69a0d23
tree8da2adc56964173cdaac4e2974121b7040e528a2tree | snapshot
parent045e3884bc432aff651659dc60059d1e8c2f86eacommit | diff
docs: clarify git-branch --list behavior

It was not clear from the "description" section of git-branch(1)
that using a <pattern> meant that you _had_ to use the --list
option. Let's clarify that, and while we're at it, reword some
clunky and ambiguous sentences.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-branch.txt diff | blob | history
Git—the stupid content tracker