git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Aschenbrenner <jonas.aschenbrenner@gmail.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: git@vger.kernel.org
Subject: Re: Suggestion to rename "blame" of the "git blame" command to something more neutral
Date: Thu, 7 Jul 2022 21:12:47 +0200	[thread overview]
Message-ID: <CADS2hGoHzx4oGxZnx-DwstKLVM7w4afcYcgmPuAb=ex3WB78iA@mail.gmail.com> (raw)
In-Reply-To: <20220707170032.GR17705@kitsune.suse.cz>

Thanks. I wasn't  aware of the fact that there is a "git annotate"
command before.
The point regarding the word "blame" seems to remain.
Maybe the "git blame" command can be removed in a future major version
and a flag added to "git annotate" so that "git annotate" can return
the data in the format in which "git blame" currently returns it.

On Thu, Jul 7, 2022 at 7:00 PM Michal Suchánek <msuchanek@suse.de> wrote:
>
> On Thu, Jul 07, 2022 at 05:35:41PM +0200, Jonas Aschenbrenner wrote:
> > 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.
>
> Have you seen git-annotate(1)
>
> Best regards
>
> Michal

  reply	other threads:[~2022-07-07 19:13 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 [this message]
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
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='CADS2hGoHzx4oGxZnx-DwstKLVM7w4afcYcgmPuAb=ex3WB78iA@mail.gmail.com' \
    --to=jonas.aschenbrenner@gmail.com \
    --cc=git@vger.kernel.org \
    --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).