git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: GitList <git@vger.kernel.org>
Subject: Re: [PATCH] doc branch: provide examples for listing remote tracking branches
Date: Tue, 28 May 2019 15:17:09 +0100	[thread overview]
Message-ID: <d44cbf49-dea9-c518-17e3-f9b252f2dd06@iee.org> (raw)
In-Reply-To: <xmqq5zpuel4m.fsf@gitster-ct.c.googlers.com>

On 28/05/2019 14:58, Junio C Hamano wrote:
> Philip Oakley <philipoakley@iee.org> writes:
>
>> The availability of these pattern selections is not obvious from
>> the man pages, as per mail thread <87lfz3vcbt.fsf@evledraar.gmail.com>.
>>
>> Provide examples.
>>
>> Signed-off-by: Philip Oakley <philipoakley@iee.org>
>> ---
> Please try again, perhaps after reading
> <CACsJy8B_3ZytR+5HvOax=ngw7ECse8_5ajkOvUEcOj3MuNxQvQ@mail.gmail.com>
Hi Junio
Sorry, I'm not understanding the comment, even having re-read the thread.
Philip
>
> Thanks.
>
>> in response to
>> <CACsJy8CwY8gzeWa9kNRX3ecez1JGiQiaOknbAoU7S+hiXBoUGQ@mail.gmail.com>
>> https://public-inbox.org/git/?q=%3CCACsJy8CwY8gzeWa9kNRX3ecez1JGiQiaOknbAoU7S%2BhiXBoUGQ%40mail.gmail.com%3E
>>
>> to: "Git Mailing List <git@vger.kernel.org>"
>> cc: "Duy Nguyen <pclouds@gmail.com>"
>> cc: "Ævar Arnfjörð Bjarmason <avarab@gmail.com>"
>>
>>   Documentation/git-branch.txt | 12 ++++++++++++
>>   1 file changed, 12 insertions(+)
>>
>> diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
>> index 3bd83a7cbd..7ed91f1be3 100644
>> --- a/Documentation/git-branch.txt
>> +++ b/Documentation/git-branch.txt
>> @@ -314,6 +314,18 @@ $ git branch -D test                                    <2>
>>   <2> Delete the "test" branch even if the "master" branch (or whichever branch
>>       is currently checked out) does not have all commits from the test branch.
>>   
>> +Listing branches from a specific remote::
>> ++
>> +------------
>> +$ git branch -a -l '<remote>/<pattern>'                 <1>
>> +$ git for-each-ref 'refs/remotes/<remote>/<pattern>'    <2>
>> +------------
>> ++
>> +<1> This can conflate <remote> with any local branches you happen to
>> +    have been prefixed with the same <remote> pattern.
>> +<2> `for-each-ref` can take a wide range of options. See linkgit:git-for-each-ref[1]
>> +
>> +Patterns will normally need quoting.
>>   
>>   NOTES
>>   -----


  reply	other threads:[~2019-05-28 14:17 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 [this message]
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=d44cbf49-dea9-c518-17e3-f9b252f2dd06@iee.org \
    --to=philipoakley@iee.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).