Re: New "make benchmark" target

[Andrea Corallo <acorallo@gnu.org>]

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Tue, 31 Dec 2024 04:00:05 +0000
>> From: Pip Cet <pipcet@protonmail.com>
>> Cc: acorallo@gnu.org, stefankangas@gmail.com, mattiase@acm.org, eggert@cs.ucla.edu, emacs-devel@gnu.org
>> 
>> "Eli Zaretskii" <eliz@gnu.org> writes:
>> 
>> >> Date: Mon, 30 Dec 2024 17:25:44 +0000
>> >> From: Pip Cet <pipcet@protonmail.com>
>> >> Cc: acorallo@gnu.org, stefankangas@gmail.com, mattiase@acm.org, eggert@cs.ucla.edu, emacs-devel@gnu.org
>> >>
>> >> "Eli Zaretskii" <eliz@gnu.org> writes:
>> >>
>> >> 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.
>> >
>> > Fine by me.
>> 
>> Pushed to scratch/elisp-benchmarks.
>
> Thanks.
>
>> Sorry for all the noise; we should really find a way to reduce
>> emacs-diffs notifications when many commits are made at once.
>
> I see no reason: people who subscribe to that list should be prepared
> for floods from time to time.
>
>> This branch:
>> 
>> 1. contains whitespace errors, because it contains the files precisely
>> as they are in the elisp-benchmarks repo
>
> We should probably clean that up, unless Andrea says that those
> whitespace are somehow needed.

Yep, I guess the best for simplicity is to push changes to
elisp-benchmarks and later to merge them into emacs-core.  AFAIR it's
also the way other packages in a similar situation operates.