From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: GitList <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH] doc branch: provide examples for listing remote tracking branches
Date: Tue, 28 May 2019 08:51:29 -0700 [thread overview]
Message-ID: <xmqqftoy60hq.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <48b03739-b8f7-4d94-15dd-cf7936215a0e@iee.org> (Philip Oakley's message of "Tue, 28 May 2019 15:51:21 +0100")
Philip Oakley <philipoakley@iee.org> writes:
> However, isn't `-r <pattern>` broken?
No.
> 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?
next prev parent reply other threads:[~2019-05-28 15:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 15:16 Command to list <pattern> Branches on a specific Remote (i.e. select from rtb's) Philip Oakley
2019-05-18 18:37 ` Ævar Arnfjörð Bjarmason
2019-05-18 19:44 ` Philip Oakley
2019-05-19 3:07 ` Duy Nguyen
2019-05-19 9:49 ` Philip Oakley
2019-05-28 12:13 ` [PATCH] doc branch: provide examples for listing remote tracking branches Philip Oakley
2019-05-28 13:58 ` Junio C Hamano
2019-05-28 14:17 ` Philip Oakley
2019-05-28 14:51 ` Philip Oakley
2019-05-28 15:51 ` Junio C Hamano [this message]
2019-05-28 16:17 ` Philip Oakley
2019-05-28 23:16 ` [RFC/PATCH v2] " Philip Oakley
2019-06-10 17:57 ` Junio C Hamano
2019-06-14 21:00 ` Philip Oakley
2019-05-19 3:05 ` Command to list <pattern> Branches on a specific Remote (i.e. select from rtb's) Duy Nguyen
2019-05-28 13:57 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqftoy60hq.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).