Let us not call it git blame

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Let us not call it git blame
From: Dinesh Dharmawardena <dinesh_dh@xxxxxxxxxxx>
Date: Thu, 2 Mar 2023 22:00:59 +0000
Accept-language: en-AU, en-US
In-reply-to: <SY6P282MB3782FD975E6F39951C5A43DA92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
References: <SY6P282MB3782FD975E6F39951C5A43DA92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
Thread-index: AQHZTVJ5pkJAaoUsPUej6bMQtlpoiw==
Thread-topic: Let us not call it git blame

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

Follow-Ups:
- Re: Let us not call it git blame
  - From: Elijah Lynn
- Re: Let us not call it git blame
  - From: Ævar Arnfjörð Bjarmason
- Re: Let us not call it git blame
  - From: Peter Hadlaw
- Re: Let us not call it git blame
  - From: demerphq
- Re: Let us not call it git blame
  - From: brian m. carlson

Prev by Date: [PATCH v9 0/6] submodule: parallelize diff
Next by Date: [PATCH v9 3/6] submodule: move status parsing into function
Previous by thread: [Failure] Re: git 2.40.0-rc1
Next by thread: Re: Let us not call it git blame
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux