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

Re: [PATCH] Add --remotes option to show-branch

From
Brian Gernhardt <benji@silverinsanity.com>
Date
Dec 19, 2006, 18:59 UTC
Message-ID
<4102F0A8-3DC4-43D1-B772-A4529D769131@silverinsanity.com>
In-Reply-To
<7vpsagtowm.fsf@assigned-by-dhcp.cox.net>
On Dec 19, 2006, at 12:50 AM, Junio C Hamano wrote:
> Actually, git show-branch origin/* would work equally well if
> you do not have local "heads/origin/*" branches.

Fair enough. I'm not strongly attached to the options for the various refs. And there is always showbranch.default. I still think that --all would be good to keep around as meaning refs/heads/* and refs/remotes/*/*, however (and NOT refs/tags/*). If nothing else, so a small-ish repository can compare everything fairly easily.

Previous: Junio C Hamano
Message 4 of 4 in “Add --remotes option to show-branch”
  1. Add --remotes option to show-branchBrian Gernhardt, Dec 18, 2006
  2. Brian GernhardtDec 19, 2006
  3. Junio C HamanoDec 19, 2006
  4. Brian GernhardtDec 19, 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.