From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2026, #05)
Date: Fri, 13 Nov 2026 16:34:32 -0800 [thread overview]
Message-ID: <xmqqcxs88d47.fsf@gitster.g> (raw)
In-Reply-To: <avehwsI-uOJ6DldC@fruit.crustytoothpaste.net> (brian m. carlson's message of "Fri, 13 Nov 2026 23:48:19 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
>> * bc/restrict-hex-to-lowercase (2026-09-07) 7 commits
>> - hex: allow only lowercase object IDs in breaking changes mode
>> - t5324: adjust tests for corrupt commit-graph
>> - object-name: use hexval
>> - hex: label usages of hex parsing for object IDs
>> - hex: make hex_to_bytes accept kind of hex to use
>> - hex: allow specifying hex type with hex2chr
>> - hex: add functionality for lowercase-only hex
>>
>> The parser for hex object names has been updated to reject uppercase
>> hexadecimal characters when running in the breaking changes mode, in
>> preparation for Git 3.0.
>>
>> Needs review.
>> source: <20260907195941.1024289-1-sandals@crustytoothpaste.net>
>
> I would love a review if someone can provide one.
Yeah, I have been saving my bandwidth and looking at other patches
after I saw somebody else volunteered (IIRC it was Patrick but I may
be misremembering).
prev parent reply other threads:[~2026-11-14 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 23:45 What's cooking in git.git (Nov 2026, #05) Junio C Hamano
2026-11-13 10:08 ` Toon Claes
2026-11-13 17:34 ` Junio C Hamano
2026-11-13 23:48 ` brian m. carlson
2026-11-14 0:34 ` 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=xmqqcxs88d47.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox