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

Re: [PATCH] pretty: allow to override the built-in formats

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 6, 2020, 21:59 UTC
Message-ID
<xmqqeene36t7.fsf@gitster.c.googlers.com>
In-Reply-To
<20200905195218.GA892287@generichostname>
Denton Liu <liu.denton@gmail.com> writes:
> Hmm, I'm not sure how I feel about being able to override formats other
> than "reference".

Is the idea to introduce a parallel namespace to pretty.<name>? I am not sure why that is a good idea than, say a single variable that says "to me, pretty.<name> would override even the built-in names".

I am not sure how I feel about being able to override built-in formats in the first place, though.

After all, pretty.<name> were introduced so that user-defined ones can be invoked with an equal ease as the built-in ones, but overriding common understanding among the users of the tool is a different story.

Previous: Denton LiuNext: Beat Bolli
Message 3 of 10 in “pretty: allow to override the built-in formats”
  1. pretty: allow to override the built-in formatsBeat Bolli, Sep 5, 2020
  2. Denton LiuSep 5, 2020
  3. Junio C HamanoSep 6, 2020
  4. Beat BolliSep 7, 2020
  5. Junio C HamanoSep 7, 2020
  6. Beat BolliSep 7, 2020
  7. Jeff KingSep 8, 2020
  8. Junio C HamanoSep 8, 2020
  9. Jeff KingSep 9, 2020
  10. Junio C HamanoSep 9, 2020

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.