Re: [PATCH v3 0/5] Expanding tabs in "git log" output

From: Torsten Bögershausen <tboegi@web.de>
Date: Mar 24, 2016, 07:05 UTC
Message-ID: <56F391A4.6090603@web.de>
In-Reply-To: <1458775426-2215-1-git-send-email-gitster@pobox.com>

>  [5/5] adds a new option --no-expand-tabs that controls the bit 4/5
>        introduces, so that "git log [--pretty] --no-expand-tabs"
>        would show the log message indented by 4 spaces, without tab
>        expansion.

Does this introduce an unnecessary regression out of the sudden ?

Would it make sense to have git log --tab-size=8 (or similar)

and add a config variable like git config ui.logtabsize which is 0 by default to get the old handling and 8 for the new one ?

$ 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.