Re: Let us not call it git blame
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Mar 2, 2023, 22:16 UTC
- Message-ID
- <ZAEgRDelTlNZRJ5J@tapette.crustytoothpaste.net>
- In-Reply-To
- <SY6P282MB378273980F5BC9084EEF74EF92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
On 2023-03-02 at 22:00:59, Dinesh Dharmawardena wrote:
> 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.
I believe there's already an alias for it, git annotate, if you'd prefer to use that. The name "blame" came in with CVS, with the synonym "annotate", so it's well understood, but you can use whichever alias you prefer.
I do think there may some differences in the defaults between git annotate and git blame, but if someone wanted to send in a patch for an option to make annotate produce identical output to blame, then I think it could be a full replacement.
-- brian m. carlson (he/him or they/them) Toronto, Ontario, CA