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

Let us not call it git blame

From
DDDinesh Dharmawardena <dinesh_dh@outlook.com>
Date
Mar 2, 2023, 22:00 UTC
Message-ID
<SY6P282MB378273980F5BC9084EEF74EF92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
In-Reply-To
<SY6P282MB3782FD975E6F39951C5A43DA92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
Hi
I am writing to you to request that the term blame in git blame be replaced with something that does not sound so blameful. I’m an SRE and we actively try promote a blameless culture as such industry tooling should also follow suit imo. Progressively phasing this term out with a better alias would be great.

Cheers Dinesh

Sent from my iPhone
Next: brian m. carlson
Message 1 of 10 in “Let us not call it git blame”
  1. Dinesh DharmawardenaMar 2, 2023
  2. brian m. carlsonMar 2, 2023
  3. Junio C HamanoMar 2, 2023
  4. rsbecker@nexbridge.comMar 3, 2023
  5. demerphqMar 3, 2023
  6. brian m. carlsonMar 3, 2023
  7. demerphqMar 3, 2023
  8. Peter HadlawMar 3, 2023
  9. Ævar Arnfjörð BjarmasonMar 7, 2023
  10. Elijah LynnMar 9, 2023

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.