13 sep. 2024 kl. 08.25 skrev Eli Zaretskii :
>> FAILED uniquify-project-transform
Looks like it fails because there is no current project in a tree that isn't
under version control.
I added a gate. Spencer, feel free to change if you want something fancier, but
I don't think we really need
7 sep. 2024 kl. 17.52 skrev Eli Zaretskii :
> OK, so let's go with unconditionally unibyte, as it seems to be the
> consensus here.
That change has now been pushed to emacs-30. Feel free to adjust as required.
1 sep. 2024 kl. 00.26 skrev Stefan Kangas :
> For symbols that are in symbol-releases.eld, which means we are actually
> sure about the addition, shouldn't the help text be changed from
>
>Probably introduced at or before Emacs version XX.Y.
>
> to something more like
>
>Added in Emacs
31 aug. 2024 kl. 12.10 skrev Eli Zaretskii :
> Should we perhaps mention this in some admin/notes/ files, like
> perhaps the procedure described in make-tarball.txt?
Not sure what to say and where so I'll leave that for others. This hack is a
bit reactive in nature, but could become a little ver
31 aug. 2024 kl. 18.07 skrev Eli Zaretskii :
> SGTM, thanks.
Thank you, push with minor tweak to emacs-30.
31 aug. 2024 kl. 14.58 skrev Eli Zaretskii :
> Doesn't that lose useful information? It only tells what is compared
> recursively, but doesn't tell about comparing strings or integers or
> bool-vectors by themselves, which is IMO important.
That's a fair point. What about something like:
The @c
Thank you for making this text better. It can be made even more accurate:
neither integers nor strings or bool-vectors are actually compared recursively
in a useful sense so we shouldn't claim that they are, and nowadays both
byte-compiled and interpreted closures are compiled but we should note
