From: "Julia Evans" <julia@jvns.ca>
To: "Junio C Hamano" <gitster@pobox.com>,
"D. Ben Knoble" <ben.knoble@gmail.com>
Cc: "Julia Evans" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Jeff King" <peff@peff.net>
Subject: Re: [PATCH] glossary: use "object ID" as the canonical term
Date: Tue, 27 Oct 2026 18:34:54 -0400 [thread overview]
Message-ID: <fbe5442b-6f01-4a23-8282-6a940b89da43@app.fastmail.com> (raw)
In-Reply-To: <xmqqh5i7j6km.fsf@gitster.g>
On Tue, Oct 27, 2026, at 3:18 PM, Junio C Hamano wrote:
> "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'll only say that I genuinely thought this might be a fairly
uncontroversial change. Obviously I was wrong about that :)
I'll drop this.
- Julia
next prev parent reply other threads:[~2026-10-27 22:35 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
2026-10-27 19:24 ` D. Ben Knoble
2026-10-27 22:34 ` Julia Evans [this message]
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=fbe5442b-6f01-4a23-8282-6a940b89da43@app.fastmail.com \
--to=julia@jvns.ca \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox