public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Marc Branchaud <marcnarc@xiplink•com>
Cc: "Raphaël Gallais-Pou" <rgallaispou@gmail•com>,
	git@vger•kernel.org, "David Aguilar" <davvid@gmail•com>,
	"Denton Liu" <liu.denton@gmail•com>,
	"Paul Mackerras" <paulus@ozlabs•org>,
	"Beat Bolli" <dev+git@drbeat•li>
Subject: Re: [PATCH] gitk: add "Hightlight commit name" menu entry
Date: Mon, 25 Mar 2024 11:56:08 -0700	[thread overview]
Message-ID: <xmqq34sekunr.fsf@gitster.g> (raw)
In-Reply-To: <742ac151-74cd-46f8-8dfb-3dcdaa513314@xiplink.com> (Marc Branchaud's message of "Mon, 25 Mar 2024 08:52:00 -0400")

Marc Branchaud <marcnarc@xiplink•com> writes:

> (BTW, on this list we pronounce "the name of the commit" as "the
> commit subject (line)".)

Yup. "subject" probably comes from the fact that the title (the
first paragraph, folded into a single line) of the commit is used on
the "Subject:" header when formatted for e-mail submission, and also
's' in "git log --pretty='%s'" is described as "subject" in the
documentation.  Other words I've seen used are "commit title" and
"oneline description", but "subject" would be the most common, I
suspect.

"commit name" on the other hand brings a different concept, i.e.,
"the commit object name", more strongly to readers' minds, and can
be mistaken as what you'd get in "git log --pretty='%H'".

      reply	other threads:[~2024-03-25 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  8:53 [PATCH] gitk: add "Hightlight commit name" menu entry Raphael Gallais-Pou
2024-03-19 19:45 ` Raphaël Gallais-Pou
2024-03-21 15:51 ` Marc Branchaud
2024-03-23  9:45   ` Raphaël Gallais-Pou
2024-03-25 12:52     ` Marc Branchaud
2024-03-25 18:56       ` Junio C Hamano [this message]

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=xmqq34sekunr.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=davvid@gmail$(echo .)com \
    --cc=dev+git@drbeat$(echo .)li \
    --cc=git@vger$(echo .)kernel.org \
    --cc=liu.denton@gmail$(echo .)com \
    --cc=marcnarc@xiplink$(echo .)com \
    --cc=paulus@ozlabs$(echo .)org \
    --cc=rgallaispou@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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