git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: demerphq <demerphq@gmail.com>
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: Fri, 3 Mar 2023 09:28:37 +0100	[thread overview]
Message-ID: <CANgJU+XT3h4b40Nr8uq_j4NyY0ka43vPghN4fJx8B=qcCHoUaA@mail.gmail.com> (raw)
In-Reply-To: <SY6P282MB378273980F5BC9084EEF74EF92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>

On Thu, 2 Mar 2023 at 23:21, Dinesh Dharmawardena <dinesh_dh@outlook.com> 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.

Just set up an alias that maps `git credit` to `git blame`, and you are done.

$ git config --global alias.credit blame

I dont think there is or ever will be much traction to rename this
command, it is short and self descriptive.

Blameless culture is great, but it is about "not finger pointing", not
about what tools you use. Your company's management and internal
culture keepers are more important for setting this tone than the
tools you use.  If they don't actually practice not finger pointing
then renaming the tool won't dont anything, and if they do actually
practice then the name of the tool won't matter either.

cheers,
Yves

-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

  parent reply	other threads:[~2023-03-03  8:29 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
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 [this message]
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='CANgJU+XT3h4b40Nr8uq_j4NyY0ka43vPghN4fJx8B=qcCHoUaA@mail.gmail.com' \
    --to=demerphq@gmail.com \
    --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).