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

Re: BUG: 'error: invalid key: pager.show_ref' on 'git show_ref'

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 6, 2015, 20:14 UTC
Message-ID
<xmqq386ihk5w.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20150206193313.GA4220@peff.net>
Jeff King <peff@peff.net> writes:
> This is highlighting the problem with "pager.*" that Junio mentioned
> recently, which is that the keyname has arbitrary data,...

Yes, even if it is not "arbitrary" (imagine we limit ourselves to the official set of commands we know about), the naming rule for the "git" subcommand names should not be dictated by the naming rule for the configuration variables, as they are unrelated.

That is one of the reasons why I had the "unbounded set, including the ones under our control such as subcommand names" in the draft update for the guideline. I dropped that part after the discussion to keep other "obviously agreed" parts moving, but we may have to revisit it later.

Previous: Jeff KingNext: Jeff King
Message 12 of 16 in “BUG: 'error: invalid key: pager.show_ref' on 'git show_ref'”
  1. Andreas KreyFeb 6, 2015
  2. Jeff KingFeb 6, 2015
  3. Junio C HamanoFeb 6, 2015
  4. Jeff KingFeb 6, 2015
  5. config: add show_err flag to git_config_parse_key()Tanay Abhra, Feb 10, 2015
  6. Jeff KingFeb 11, 2015
  7. Junio C HamanoFeb 11, 2015
  8. add a flag to supress errors in git_config_parse_key()Tanay Abhra, Feb 16, 2015
  9. Jeff KingFeb 18, 2015
  10. Mikael MagnussonFeb 7, 2015
  11. Jeff KingFeb 7, 2015
  12. Junio C HamanoFeb 6, 2015
  13. Jeff KingFeb 6, 2015
  14. Junio C HamanoFeb 6, 2015
  15. Junio C HamanoFeb 6, 2015
  16. Jeff KingFeb 7, 2015

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.