All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Aleks Todorov <aleks.todorov.1337@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Add Commit Summary in blame?
Date: Fri, 05 Apr 2024 17:19:03 -0700	[thread overview]
Message-ID: <xmqqzfu7s5qg.fsf@gitster.g> (raw)
In-Reply-To: <CAO0eup=KqHe68OkHqYWtDgsTx0cAwg5Y5HSqK4s_BNbZhr8hVw@mail.gmail.com> (Aleks Todorov's message of "Sat, 6 Apr 2024 00:07:58 +0100")

Aleks Todorov <aleks.todorov.1337@gmail.com> writes:

> Would people be interested in seeing a patch that adds an option to
> see the commit message summary line in the git blame output? I imagine
> I'm not the first person to come up with this, is there a reason why
> it wasn't already implemented? The porcelain already has it, so the
> change is trivial.

I personally do not.  The blame output on the left-hand-side is
already wide enough to be even annoying.

A patch that might interest me personally would be one that takes
the --format option (copy from the log family plus add some that are
only useful in "git blame", like "line number") to allow customizing
the left-hand-side of the output, and allows us to reimplement ugly
hacks^W^W ad-hoc options (like -l, -t, --date, -f, -n, -s, -e) in
terms of that.  With such a feature, of course your "commit summary"
will come almost for free in the form of --format=%s I would think.

A change that adds even more ad-hoc options is probably not welcome,
I would have to say.



  reply	other threads:[~2024-04-06  0:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 23:07 Add Commit Summary in blame? Aleks Todorov
2024-04-06  0:19 ` Junio C Hamano [this message]
2025-02-16 21:13   ` Aleks Todorov
2025-02-18 18:08     ` 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=xmqqzfu7s5qg.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=aleks.todorov.1337@gmail.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.
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.