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

Re: [PATCH] git-gui: do not end the commit message with an empty line

From
Johannes Sixt <j6t@kdbg.org>
Date
May 15, 2025, 05:36 UTC
Message-ID
<049648a9-5580-4214-bd00-c905127939b5@kdbg.org>
In-Reply-To
<xmqqv7q27v49.fsf@gitster.g>
Am 14.05.25 um 23:14 schrieb Junio C Hamano:
> As git-gui uses plumbing commit-tree to create the
> commit object, it has to be more careful not to have extra blank
> lines, as it cannot assume stripspace internal to "git commit"?

Correct. We had used git stripspace for about a month, introduced by b9a4386, reverted by c0698df. The reasons not to use it were old Tcl versions and MacOS. We may revisit this case after we raise version requirements.

-- Hannes
Previous: Junio C HamanoNext: Oswald Buddenhagen
Message 3 of 5 in “git-gui: do not end the commit message with an empty line”
  1. git-gui: do not end the commit message with an empty lineJohannes Sixt, May 14, 2025
  2. Junio C HamanoMay 14, 2025
  3. Johannes SixtMay 15, 2025
  4. Oswald BuddenhagenMay 15, 2025
  5. git-gui: do not end the commit message with an empty lineJohannes Sixt, May 15, 2025

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.