git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Jonas Aschenbrenner" <jonas.aschenbrenner@gmail.com>,
	git@vger.kernel.org
Subject: Re: Suggestion to rename "blame" of the "git blame" command to something more neutral
Date: Sun, 10 Jul 2022 09:35:43 -0700	[thread overview]
Message-ID: <xmqq1qutrkm8.fsf@gitster.g> (raw)
In-Reply-To: <20220710145502.GT17705@kitsune.suse.cz> ("Michal =?utf-8?Q?S?= =?utf-8?Q?uch=C3=A1nek=22's?= message of "Sun, 10 Jul 2022 16:55:02 +0200")

Michal Suchánek <msuchanek@suse.de> writes:

>> What do you think about this old patch of mine to add a 'git praise'?:
>> https://lore.kernel.org/git/20190401101246.21418-1-avarab@gmail.com/
>
> Since you are asking .. I think it completely misses the point.
>
> I would consider it effective if users of git-praise(1) needed no
> knowledge of existence of git-blame(1).

I think you are the one who completely misses the point of him
sending the URL (hint: what is the date of the patch?)

"blame" is perfectly fine.  It is the tool we use to find a commit
or a series of commits to be blamed for whichever blocks of code in
the current codebase we are interested in.  Even if it is to find
the source of the buggy or ugly code in the current codebase
(i.e. "verb with negative connotation"), we are trying to put our
fingers on the commit to be blamed.

And it is not personal---you may find who the "author" was as a side
effect of finding that offending commit, but authors write both good
and bad commits, and what we are trying to find is in which commit
lies the origin of the current badness.  There is no need to be
overly politically correct by bending the verb we use.

Please do not waste our limited engineering resource on a nonsense
like this.  A solution for whoever do not want to type b l a m e has
already been provided upthread and the discussion should end right
there.

Thanks.



  reply	other threads:[~2022-07-10 16:35 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
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 [this message]
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=xmqq1qutrkm8.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jonas.aschenbrenner@gmail.com \
    --cc=msuchanek@suse.de \
    /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 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 NNTP newsgroup(s).