From: Philip Oakley Date: Tue, 28 May 2019 14:17:09 GMT Subject: Re: [PATCH] doc branch: provide examples for listing remote tracking branches Message-ID: In-Reply-To: On 28/05/2019 14:58, Junio C Hamano wrote: > Philip Oakley 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 >> --- > Please try again, perhaps after reading > Hi Junio Sorry, I'm not understanding the comment, even having re-read the thread. Philip > > Thanks. > >> in response to >> >> https://public-inbox.org/git/?q=%3CCACsJy8CwY8gzeWa9kNRX3ecez1JGiQiaOknbAoU7S%2BhiXBoUGQ%40mail.gmail.com%3E >> >> to: "Git Mailing List " >> cc: "Duy Nguyen " >> cc: "Ævar Arnfjörð Bjarmason " >> >> 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 '/' <1> >> +$ git for-each-ref 'refs/remotes//' <2> >> +------------ >> ++ >> +<1> This can conflate with any local branches you happen to >> + have been prefixed with the same 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 >> -----