From: Philip Oakley <philipoakley@iee.org>
To: Duy Nguyen <pclouds@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Command to list <pattern> Branches on a specific Remote (i.e. select from rtb's)
Date: Sun, 19 May 2019 10:49:53 +0100 [thread overview]
Message-ID: <a83183ec-a87a-b080-6e72-489e7fc1ebd6@iee.org> (raw)
In-Reply-To: <CACsJy8CwY8gzeWa9kNRX3ecez1JGiQiaOknbAoU7S+hiXBoUGQ@mail.gmail.com>
On 19/05/2019 04:07, Duy Nguyen wrote:
> On Sun, May 19, 2019 at 2:55 AM Philip Oakley <philipoakley@iee.org> wrote:
>> I'll add the answer to one on the stackoverflow Q&A's I'd looked at. I
>> hadn't put the branch -a and -l options together.
> Maybe update/add some examples in our man pages too.
deffo on an update! For the -r option I did not expect to be able to add
a remote name (no option listed, nor method noted).
Just re-read the branch(1) man page and much of it is buried in the
first paragraph with/for the --list option with lots of caveats and
pairings.
--
Philip
next prev parent reply other threads:[~2019-05-19 17:40 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 [this message]
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
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=a83183ec-a87a-b080-6e72-489e7fc1ebd6@iee.org \
--to=philipoakley@iee.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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).