Re: What's cooking in git.git (Nov 2026, #05)

["brian m. carlson" <sandals@crustytoothpaste.net>]

[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]

On 2026-11-12 at 23:45:18, Junio C Hamano wrote:
> * bc/setup-default-hash-algo (2026-11-07) 1 commit
>  - setup: default hash algo to GIT_HASH_DEFAULT
> 
>  The object format initialization in 'git init' has been updated to
>  use the default hash algorithm compiled into the binary, ensuring
>  new repositories use 'sha256' when breaking changes are enabled.
>  Waiting for response.
>  cf. <xmqqik274201.fsf@gitster.g>
>  source: <20261108011633.1772000-1-sandals@crustytoothpaste.net>

I just sent a v2 of this.

> * 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.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Speaking for myself only

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]