[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New "make benchmark" target
From: |
Pip Cet |
Subject: |
Re: New "make benchmark" target |
Date: |
Sun, 05 Jan 2025 10:18:02 +0000 |
"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!
Pip
- Re: New "make benchmark" target, Pip Cet, 2025/01/04
- Re: New "make benchmark" target, Eli Zaretskii, 2025/01/04
- Re: New "make benchmark" target,
Pip Cet <=
- Re: New "make benchmark" target, Stefan Kangas, 2025/01/15
- Re: New "make benchmark" target, Eli Zaretskii, 2025/01/16
- Re: New "make benchmark" target, Andrea Corallo, 2025/01/17
- Re: New "make benchmark" target, Pip Cet, 2025/01/17
- Re: New "make benchmark" target, Andrea Corallo, 2025/01/17
- Re: New "make benchmark" target, Pip Cet, 2025/01/17
- Re: New "make benchmark" target, Andrea Corallo, 2025/01/18
- Re: New "make benchmark" target, Pip Cet, 2025/01/18
- Re: New "make benchmark" target, Andrea Corallo, 2025/01/18
- Re: New "make benchmark" target, Pip Cet, 2025/01/19