git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Possible BUG with git-rev-list --all in a StGit repository

From
Junio C Hamano <junkio@cox.net>
Date
Nov 27, 2006, 07:25 UTC
Message-ID
<7vzmadl5b0.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<e5bfff550611262238q60d466a3r230c9c4af283b76b@mail.gmail.com>
"Marco Costalba" <mcostalba@gmail.com> writes:
> Could a possible '--all-branches' new option come to rescue?

I doubt it. Next thing people would start talking about is what to do with the remote tracking branches, and what we are talking about is rev-list, one of the lower level of plumbing that would be better left without knowing much about the Porcelain's use of refs/ namespaces.

If you (as a Porcelain) want to get all refs under refs/heads/, there are (unfortunately) two ways to get that list. I would suggest obtain the refs you want that way, pass them as command line arguments to rev-list.

$ git for-each-ref --format='%(refname)' refs/heads $ git show-ref --heads | sed -e 's/^[^ ]* //'

Previous: Marco CostalbaNext: Sergey Vlasov
Message 5 of 10 in “Possible BUG with git-rev-list --all in a StGit repository”
  1. Marco CostalbaNov 26, 2006
  2. Junio C HamanoNov 26, 2006
  3. Marco CostalbaNov 27, 2006
  4. Marco CostalbaNov 27, 2006
  5. Junio C HamanoNov 27, 2006
  6. revision traversal: Add --refs=<pattern> optionSergey Vlasov, Nov 27, 2006
  7. Junio C HamanoNov 27, 2006
  8. Marco CostalbaNov 28, 2006
  9. Junio C HamanoNov 28, 2006
  10. Marco CostalbaNov 28, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.