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

2013-01-31 Thread Eric Sunshine
On Thu, Jan 31, 2013 at 1:45 AM, Jeff King p...@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

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

2013-01-31 Thread Junio C Hamano
Eric Sunshine sunsh...@sunshineco.com writes: On Thu, Jan 31, 2013 at 1:45 AM, Jeff King p...@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

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

2013-01-31 Thread Jeff King
On Thu, Jan 31, 2013 at 04:37:01PM -0800, Junio C Hamano wrote: Eric Sunshine sunsh...@sunshineco.com writes: On Thu, Jan 31, 2013 at 1:45 AM, Jeff King p...@peff.net wrote: +If `--list` is given, or if there are no non-option arguments, existing +branches are listed; the current branch

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

2013-01-31 Thread Junio C Hamano
Jeff King p...@peff.net writes: Thanks. No matter how many times I proofread a doc change, I always manage to slip an error into the final version. I think everybody shares that trait. Hooray for many eyes. Indeed. -- To unsubscribe from this list: send the line unsubscribe git in the body

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

2013-01-30 Thread Jeff King
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 p...@peff.net --- Documentation/git-branch.txt | 16