Re: New "make benchmark" target

[Stefan Kangas]

Pip Cet <pipcet@protonmail.com> writes:

> "Eli Zaretskii" <eliz@gnu.org> writes:
>
>>> I'm happy to change the scratch/elisp-benchmarks branch in the ways
>>> we've discussed, and it should be merged, but if someone decides to
>>> incrementally solve some of the issues, that, while not very harmful,
>>> would be an inefficient use of resources.
>>
>> Let's hear what Andrea thinks about the issues you reported (let's
>> please discuss them on the bug tracker, not here), and let's take it
>> from there.
>
> Sure, just let me know when we can merge the branch (assuming you meant
> to say that the merge, too, should wait for Andrea's thoughts) or which
> other changes are required!

Is there anything left to do here that is blocking the merge?

> Top-posted TL;DR: let's call Andrea's code "make elisp-benchmarks" and
> include it now?  That would preserve the Git history and importantly (to
> me) reserve the name for now.

Sounds good to me.  We can discuss changing things further after the merge.