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

Re: [PATCH] Colourise git-branch output

From
Sean <seanlkml@sympatico.ca>
Date
Dec 12, 2006, 01:24 UTC
Message-ID
<BAYC1-PASMTP092A9E80667F373BF69AA6AED70@CEZ.ICE>
In-Reply-To
<7v7iwx2a0z.fsf@assigned-by-dhcp.cox.net>

On Mon, 11 Dec 2006 17:11:24 -0800 Junio C Hamano <junkio@cox.net> wrote:

Show 7 quoted lines
> > As Junio already highlighted, the "branch.*" namespace is for actual
> > branch names.  This config option should go into "color.branch" or some
> > other spot.
> 
> I didn't.  And "branch.color = auto" is actually fine.
> 
> The problematic case is "branch.color.remote = purple".

Technically it is workable.. but why even start down the road of having anything but branch names after a "branch."? There has to be a better spot for this variable, and it makes it more future proof, as you highlighted.

Previous: Junio C HamanoNext: Linus Torvalds
Message 5 of 9 in “Colourise git-branch output”
  1. Colourise git-branch outputAndy Parkins, Dec 11, 2006
  2. Junio C HamanoDec 11, 2006
  3. SeanDec 12, 2006
  4. Junio C HamanoDec 12, 2006
  5. SeanDec 12, 2006
  6. Linus TorvaldsDec 12, 2006
  7. Junio C HamanoDec 12, 2006
  8. Linus TorvaldsDec 12, 2006
  9. Junio C HamanoDec 12, 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.