On Wed, May 8, 2019 at 10:23 AM Junio C Hamano <gits...@pobox.com> wrote:
> * en/unicode-in-refnames (2019-04-26) 1 commit > - Honor core.precomposeUnicode in more places > > The names of the refs stored as filesystem entities may become > different from what the end-user expects, just like files in the > working tree gets "renamed", on a filesystem like HFS+. Work it > around by paying attemption to the core.precomposeUnicode > configuration. > > Looked sensible. Ready for next? I believe so. en/unicode-in-refnames represents v2; the last "What's cooking?" email went out with v1 and I responded that a small commit message cleanup was needed as per Torsten's review, but that was the only issue I was aware of. However, I think your summary of this topic still needs some minor wording/spelling corrections; here's your summary with my suggested revisions: On a filesystem like HFS+, the names of the refs stored as filesystem entities may become different from what the end-user expects, just like files in the working tree get "renamed". Work around the mismatch by paying attention to the core.precomposeUnicode configuration.
