Re: [PATCH v2 0/7] Git 3.0: restrict hex object IDs to lowercase only
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 2, 2026, 09:11 UTC
- Message-ID
- <xmqq7bivmwct.fsf@gitster.g>
- In-Reply-To
- <20260907195941.1024289-1-sandals@crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
Show 6 quoted lines
> As far as I can tell, Git has always emitted hex object IDs in > lowercase, but our object ID parser accepts both uppercase and > lowercase. This leads to much software relying on hex object IDs being > broken because it doesn't handle uppercase object IDs and this can even > lead to security problems when people assume that an object ID has a > unique hex form.
As far as I can recall, this had quite a lot of discussion during v1 (or was it RFC?) but nobody seems to have been reacted to this round. Can anybody give it an eyeball (or two) and tell us that the iteration now is in line with what was discussed during the review of the previous round, so that we can mark it for 'next'?
Thanks.