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

Re: [PATCH 3/3] gitk: set log.graph=false when running `git log`

From
Alex Henrie <alexhenrie24@gmail.com>
Date
Feb 10, 2022, 16:50 UTC
Message-ID
<CAMMLpeRf=BV3y2AF7AssOw3tOFn-hawsyhFaxLhCrz28kbq+NA@mail.gmail.com>
In-Reply-To
<xmqqzgmz7v6k.fsf@gitster.g>
On Wed, Feb 9, 2022 at 11:26 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> This may handle "gitk", but what about thousands other scripts
> people have developed around "git log", I have to wonder.

That's true, but every new preference carries that risk, and there's not much we can do about it. Users who set log.graph=true will just have to accept that it won't be compatible with every tool in the wild.

-Alex
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 9 in “log: fix memory leak if --graph is passed multiple times”
  1. 1/3 log: fix memory leak if --graph is passed multiple timesAlex Henrie, Feb 9, 2022
  2. 2/3 log: add a config option for --graphAlex Henrie, Feb 9, 2022
  3. Junio C HamanoFeb 9, 2022
  4. Alex HenrieFeb 10, 2022
  5. 3/3 gitk: set log.graph=false when running `git log`Alex Henrie, Feb 9, 2022
  6. Junio C HamanoFeb 9, 2022
  7. Alex HenrieFeb 10, 2022
  8. Junio C HamanoFeb 10, 2022
  9. Junio C HamanoFeb 9, 2022

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.