Re: [PATCH v2 0/7] Improved infrastructure for refname normalization
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:52:01
Michael Haggerty [off-list ref] writes:
Consistency of the UI should be the goal. Supporting unnormalized refnames some places, but not others, will just confuse and frustrate users. ... So I propose the following: * Institute a policy that refnames in the UI must always be normalized * On a best-effort basis, emit errors whenever unnormalized refnames are encountered * Continue to support "git check-ref-format --print", which script writers can use to normalize refnames if they need to. The only disadvantage of a stricter policy is that some of today's sloppy scripts, which today might sometimes work (but not reliably), break in a pretty obvious way that can be fixed with a single call to "git check-ref-format --print". I'd rather get beyond this swamp and start working on the hierarchical reference cache, which will bring some real benefits. (The hierarchical reference cache requires some sanity in refname handling, which is why I got into this mess in the first place.)
Both the analysis and theproposal I find very sane and sensible. Thanks.