All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org,  Jeff King <peff@peff.net>,
	 Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH] glossary: use "object ID" as the canonical term
Date: Tue, 27 Oct 2026 12:18:17 -0700	[thread overview]
Message-ID: <xmqqh5i7j6km.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CCGLFwFH73of8QHnsvFjHZ8d86CRhQgV88z=WeKun6abg@mail.gmail.com> (D. Ben Knoble's message of "Tue, 27 Oct 2026 14:00:12 -0400")

"D. Ben Knoble" <ben.knoble@gmail.com> writes:

> I can't speak for Julia, but I read her attempt here to clarify things
> in line with the ways folks usually use "ID" vs. "name." Of course we
> don't always want to let what other people say dictate our
> terminology, but in cases where we can make things easier for folks to
> understand by using vocabulary in line with their expectations rather
> than subverting it, I think that's a worthy goal.

That goes both ways.  You can tell that to those who are subverting
terminology that have clearly been documented for the past 20 years
in our official glossary ;-).

> I still find it strange to call "main" an object ID ;) even if our
> current terminology says that's fine. Heck, the glossary says a name
> is a "unique" identifier… so there ought not to be more than one way
> to spell it, even if there are many notations to refer to it? Alas…

I do not think it is OK.  "main" is *NOT* an object ID or object
name.  "main" can be used where an object name or object identifier
is called for to uniquely specify an object.



  parent reply	other threads:[~2026-10-27 19:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 13:06 [PATCH] glossary: use "object ID" as the canonical term Julia Evans via GitGitGadget
2026-10-26 17:08 ` Junio C Hamano
2026-10-27 12:15 ` Ben Knoble
2026-10-27 17:47   ` Junio C Hamano
2026-10-27 18:00     ` D. Ben Knoble
2026-10-27 18:03       ` D. Ben Knoble
2026-10-27 19:18       ` Junio C Hamano [this message]
2026-10-27 19:24         ` D. Ben Knoble
2026-10-27 22:34         ` Julia Evans
2026-10-28  1: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=xmqqh5i7j6km.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=julia@jvns.ca \
    --cc=peff@peff.net \
    /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.