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

Re: [PATCH 1/2] log.decorate: accept 0/1 bool values

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 18, 2010, 17:00 UTC
Message-ID
<7vmxp6d0te.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20101117195259.GA13008@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I don't think it is worth closing the hole for no reason on other config
> options, but I am certainly fine with breaking it in the case of
> pager.*.

Hmm, I guess that is fine, but will we hear "Why does it behave differently only for pager.*" down the line, just like the issue your patch 1/2 addressed, which was "Why does it behave differently only for log.decorate?"

Previous: Jeff KingNext: Jeff King
Message 5 of 6 in “log.decorate: accept 0/1 bool values”
  1. 1/2 log.decorate: accept 0/1 bool valuesJeff King, Nov 17, 2010
  2. 2/2 allow command-specific pagers in pager.<cmd>Jeff King, Nov 17, 2010
  3. Junio C HamanoNov 17, 2010
  4. Jeff KingNov 17, 2010
  5. Junio C HamanoNov 18, 2010
  6. Jeff KingNov 18, 2010

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.