bug#65997: 29.1; ?\N{char_name} reference is wrong

[Stefan Monnier]

> it only took 9 years, but this is no longer true:
>
> lisp/international/mule-cmds.el:
>
>               ;; In theory this code could end up pushing an "old-name" that
>               ;; shadows a "new-name" but in practice every time an
>               ;; `old-name' conflicts with a `new-name', the newer one has a
>               ;; higher code, so it gets pushed later!
>
> The patch below fixes that issue.

Please adjust the patch so it correct the comment as well :-)


        Stefan