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

"discard!" commit message for commits that should be removed while cleaning up the history

From
Simon Richter <simon.richter@hogyros.de>
Date
Jul 12, 2026, 05:54 UTC
Message-ID
<07c9811e-41db-473e-ba0a-cdcbf8187be7@hogyros.de>
Hi,

I often add printf statements during debugging, which obviously should not end up in the final submission. My usual approach is to commit these immediately, into commits with a message of "DISCARD", so that when I do a final rebase pass, I can remove the debug code easily.

Would it make sense to add a mechanism that autosquash understands directly, and that could be checked for by a push hook or CI rule?

    Simon
Next: Junio C Hamano
Message 1 of 2 in “"discard!" commit message for commits that should be removed while cleaning up the history”
  1. Simon RichterJul 12, 2026
  2. Junio C HamanoJul 12, 2026

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.