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

Re: [PATCH] commit: Add commit.signoff configuration option

From
Chris Down <chris@chrisdown.name>
Date
May 15, 2025, 13:22 UTC
Message-ID
<aCXqqj6gKc7-fjoF@chrisdown.name>
In-Reply-To
<xmqqy0uy4thk.fsf@gitster.g>
Junio C Hamano writes:
>But an old mistake is never an excuse that we can pile more mistakes
>of the same kind on top.  Otherwise we wouldn't have learned anything.

I'm curious about what specific issues format.signoff has caused that make you consider it a mistake. Has there been evidence over the past 16 years of it undermining the significance of signoffs or creating other problems?

Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 14 in “commit: Add commit.signoff configuration option”
  1. commit: Add commit.signoff configuration optionChris Down, May 13, 2025
  2. Kristoffer HaugsbakkMay 13, 2025
  3. D. Ben KnobleMay 13, 2025
  4. Chris DownMay 14, 2025
  5. Junio C HamanoMay 15, 2025
  6. Chris DownMay 15, 2025
  7. Junio C HamanoMay 16, 2025
  8. Chris DownMay 16, 2025
  9. Chris DownJun 3, 2025
  10. Junio C HamanoJun 4, 2025
  11. Collin FunkJun 5, 2025
  12. Chris DownJun 9, 2025
  13. Ben KnobleMay 16, 2025
  14. Chris DownMay 16, 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.