From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>
Subject: Re: [RFC PATCH 4/6] hex: label usages of hex parsing for object IDs
Date: Thu, 30 Jul 2026 20:24:54 -0700 [thread overview]
Message-ID: <xmqq1pcjkfi1.fsf@gitster.g> (raw)
In-Reply-To: <20260729233215.398654-5-sandals@crustytoothpaste.net> (brian m. carlson's message of "Wed, 29 Jul 2026 23:32:13 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> In preparation for a future change, label the hex parsing we're doing
> for object IDs by defining a constant called HEX_KIND_OID. This is
> currently the same as HEX_KIND_MIXED, so there is no functional change
> here.
>
> Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
> ---
> diagnose.c | 2 +-
> hex-ll.h | 2 ++
> hex.c | 2 +-
> http-push.c | 4 ++--
> notes.c | 2 +-
> object-file.c | 2 +-
> 6 files changed, 8 insertions(+), 6 deletions(-)
OK. It makes sense to say "we are reading object names", than "we
are reading hex spelled in both cases". Are we throwing the "not
object names but derived from the same hash function" things like
packname and rerere database key into the same category?
> diff --git a/diagnose.c b/diagnose.c
> index fc11cea229..9c652d36a6 100644
> --- a/diagnose.c
> +++ b/diagnose.c
> @@ -112,7 +112,7 @@ static void loose_objs_stats(struct strbuf *buf, const char *path)
> while ((e = readdir_skip_dot_and_dotdot(dir)) != NULL)
> if (get_dtype(e, &count_path, 0) == DT_DIR &&
> strlen(e->d_name) == 2 &&
> - !hex_to_bytes(&c, e->d_name, 1, HEX_KIND_MIXED)) {
> + !hex_to_bytes(&c, e->d_name, 1, HEX_KIND_OID)) {
> strbuf_setlen(&count_path, base_path_len);
> strbuf_addf(&count_path, "%s/", e->d_name);
> total += (count = count_files(&count_path));
next prev parent reply other threads:[~2026-07-31 3:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 23:32 [RFC PATCH 0/6] Git 3.0: restrict hex object IDs to lowercase only brian m. carlson
2026-07-29 23:32 ` [RFC PATCH 1/6] hex: add functionality for lowercase-only hex brian m. carlson
2026-07-31 7:38 ` Junio C Hamano
2026-07-29 23:32 ` [RFC PATCH 2/6] hex: allow specifying hex type with hex2chr brian m. carlson
2026-07-29 23:32 ` [RFC PATCH 3/6] hex: make hex_to_bytes accept kind of hex to use brian m. carlson
2026-07-31 7:38 ` Junio C Hamano
2026-07-29 23:32 ` [RFC PATCH 4/6] hex: label usages of hex parsing for object IDs brian m. carlson
2026-07-31 3:24 ` Junio C Hamano [this message]
2026-07-29 23:32 ` [RFC PATCH 5/6] object-name: use hexval brian m. carlson
2026-07-29 23:32 ` [RFC PATCH 6/6] hex: allow only lowercase object IDs in breaking changes mode brian m. carlson
2026-07-31 7:48 ` Junio C Hamano
2026-07-30 8:21 ` [RFC PATCH 0/6] Git 3.0: restrict hex object IDs to lowercase only Junio C Hamano
2026-07-30 21:18 ` brian m. carlson
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=xmqq1pcjkfi1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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.