All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonas Aschenbrenner <jonas.aschenbrenner@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Suggestion to rename "blame" of the "git blame" command to something more neutral
Date: Thu, 07 Jul 2022 14:03:46 -0700	[thread overview]
Message-ID: <xmqq8rp4zlcd.fsf@gitster.g> (raw)
In-Reply-To: <CADS2hGpnkiPzivVDyN-PnGsQCTafqx68PxigXvBK1bv4O=p4kg@mail.gmail.com> (Jonas Aschenbrenner's message of "Thu, 7 Jul 2022 17:35:41 +0200")

Jonas Aschenbrenner <jonas.aschenbrenner@gmail.com> writes:

> Similar to the change of the default branch name from "master" to
> "main" to use a word which has less negative associations,
> I suggest to replace the word "blame" with something more neutral.
> Maybe "annotate". That word seems to already be used at some places
> for this Git feature.

We can help you to match the tool for your personal preference, e.g.

    $ git config --global alias.praise blame
    $ git praise COPYING

Changing what has been known for one name for a long time for other
people takes a lot more than "I do not like the word with negative
connotations".

  parent reply	other threads:[~2022-07-07 21:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 15:35 Suggestion to rename "blame" of the "git blame" command to something more neutral Jonas Aschenbrenner
2022-07-07 17:00 ` Michal Suchánek
2022-07-07 19:12   ` Jonas Aschenbrenner
2022-07-07 21:03 ` Junio C Hamano [this message]
2022-07-10 13:00 ` Reto
2022-07-10 14:31 ` Ævar Arnfjörð Bjarmason
2022-07-10 14:55   ` Michal Suchánek
2022-07-10 16:35     ` Junio C Hamano
2022-07-10 18:01       ` Michal Suchánek
2022-07-10 18:26         ` rsbecker
2022-07-11 11:47       ` Ævar Arnfjörð Bjarmason
2022-07-11 19:21         ` Junio C Hamano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq8rp4zlcd.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jonas.aschenbrenner@gmail.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.