From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Dinesh Dharmawardena <dinesh_dh@outlook.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Let us not call it git blame
Date: Thu, 2 Mar 2023 22:16:36 +0000 [thread overview]
Message-ID: <ZAEgRDelTlNZRJ5J@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <SY6P282MB378273980F5BC9084EEF74EF92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2023-03-02 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SY6P282MB3782FD975E6F39951C5A43DA92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
2023-03-02 22:00 ` Let us not call it git blame Dinesh Dharmawardena
2023-03-02 22:16 ` brian m. carlson [this message]
2023-03-02 23:47 ` Junio C Hamano
2023-03-03 0:07 ` rsbecker
2023-03-03 8:55 ` demerphq
2023-03-03 1:31 ` brian m. carlson
2023-03-03 8:28 ` demerphq
2023-03-03 18:28 ` Peter Hadlaw
2023-03-07 12:08 ` Ævar Arnfjörð Bjarmason
2023-03-09 20:28 ` Elijah Lynn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZAEgRDelTlNZRJ5J@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=dinesh_dh@outlook.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).