From: Philip Oakley <philipoakley@iee.org>
Date: Tue, 28 May 2019 16:17:49 GMT
Subject: Re: [PATCH] doc branch: provide examples for listing remote tracking branches
Message-ID: <2ea35ad4-4b33-0ece-4de4-b2e92a100d9a@iee.org>
In-Reply-To: <xmqqftoy60hq.fsf@gitster-ct.c.googlers.com>

On 28/05/2019 16:51, Junio C Hamano wrote:
> Philip Oakley <philipoakley@iee.org> writes:
>
>> However, isn't `-r <pattern>` broken?
> No.
Then why does it say:
     fatal: -a and -r options to 'git branch' do not make sense with a 
branch name

when there is no `-a` given?
>
>> phili@Philip-Win10 MINGW64 /c/git-sdk-64/usr/src/git (branch-patterns)
>> $ git branch -a -l 'junio/*'
> You are asking "branch --all --list" here.
>
>> $ git branch -a -r 'junio/*'
>> fatal: -a and -r options to 'git branch' do not make sense with a
>> branch name
> You wanted to ask "branch --remote --list" instead of "branch --all
> --remote", no?
>
The initial expectation was that a simple "--remote <pattern>" would be 
all that was required to list the rtbs with the sub-pattern (see fatal 
above, which is maybe how Ævar got his -a formulation). But it now 
appears that we/I need the --list, to allow a pattern, and either -a, or 
-r, to include the rtbs in the list.

So ultimately, yes, to just get the rtbs of a specific remote one needs 
your "branch --remote --list `<remote>/*' "formulation.

Philip