Web lists-archives.com

Re: [PATCH] doc branch: provide examples for listing remote tracking branches

On 28/05/2019 14:58, Junio C Hamano wrote:
Philip Oakley <philipoakley@xxxxxxx> writes:

The availability of these pattern selections is not obvious from
the man pages, as per mail thread <87lfz3vcbt.fsf@xxxxxxxxxxxxxxxxxxx>.

Provide examples.

Signed-off-by: Philip Oakley <philipoakley@xxxxxxx>
Please try again, perhaps after reading
Hi Junio
Sorry, I'm not understanding the comment, even having re-read the thread.


in response to

to: "Git Mailing List <git@xxxxxxxxxxxxxxx>"
cc: "Duy Nguyen <pclouds@xxxxxxxxx>"
cc: "Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx>"

  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.